Skip to content

Get Trades
deprecated

Request

NOTE: This endpoint is not supported anymore. Please have a look at Trades v3

Get trades filtered on own orders or not with the my-parameter and date based on start and end.

In the Trade endpoint, we have introduced pagination. The reason is that when you apply no filters your request won’t be time-out and you won’t be overloaded with data. When you don’t provide any parameters, the application will return with the last 100 trades and give you the option to get the next 100 trades. To do this you use the cursor parameter with nextCursor value that has been given to you from the response.

It makes use of pagination V1.0

Security
api-key
Query
cursorstring

nextCursor provided by the response of a previous request.

countinteger, (int32), [ 1 .. 100 ]

Number of trades to return. A number between 1 and 100.

Default:100
my_own_tradesboolean

Return only your own trades or only trades that are not yours. A trade is considered your own trade if you were the buyer or the seller.

participantIdstring

Filter on participantId. This is only useful for brokers.

orderIdstring

Filter on orderId.

tradeIdstring

Filter on tradeId.

startinteger, (int64), >= 0

Return trades created after the given timestamp. Value must be a Unix timestamp in milliseconds.

endinteger, (int64), >= 0

Return trades created before the given timestamp. Value must be a Unix timestamp in milliseconds.

fieldstring

The field to filter on start and/or end if specified

Default:"EXECUTED"
Enum:"START""END""EXECUTED"
timeblocksstring

Filter on timeblocks.

Enum:"INTRADAY""EXPOST""GOPACS"
GET
/public-api/2.0/electricity/trades
curl -i -X GET \
  'https://acc-trading.etpa.nl/public-api/2.0/electricity/trades?cursor=string&count=100&my_own_trades=true&participantId=string&orderId=string&tradeId=string&start=0&end=0&field=START&timeblocks=INTRADAY' \
  -H 'api_key: YOUR_API_KEY_HERE'

Responses

Requested trades

Bodyapplication/json
dataArray of objects(TradeApiResponseV2)required
nextCursorstring
Response
{
  "data": [
    { … }
  ],
  "nextCursor": "string"
}