Resources / Changelog

Changelog

We just deployed two additions to the /orders endpoint. The API now additionally returns estimated_price_total and executed_price_total, which is the estimated/executed price, multiplied by the order quantity. See the GET /orders endpoint for more information.

We added the 'idempotency' element to the orders endpoint, which allows you to create your custom idempotency key that you can add to the POST /orders request to avoid duplicate execution. See the POST /orders endpoint for more information.

We will remove the 'type' attribute from all /spaces endpoints by the beginning of next week. This includes the POST, GET and PUT endpoints. See the /spaces page for information on the updated API requests and responses.

We deployed some additions to the /orders endpoint. The API now additionally returns the response elements key_creation_id and key_activation_id. It is now also possible to filter via the API Key the order was created with using the query parameter ?key_creation_id="YOUR-API-KEY". See the GET /orders docs section for specific information.

The API now additionally returns all regulatory information in the GET /orders and GET /orders/{order_id}/ endpoints. See the GET /orders docs section for specific information.

We just added the "mode" attribute to all endpoint responses in the Trading API. The attribute tells you wether a request was performed in the Paper Money Environment ("mode: "paper") or in the Real Money Environment ("mode":"money").

Additionally, we added the "created_at" attribute to the /bankstatements endpoint response. The attribute tells you the timestamp the the account activity was created at.

We just deployed the /account/bankstatements endpoint, which gives you a detailed overview of all activities happening on your account. In that context we will deprecate the /transactions endpoint soon, as all information on account activity is now available through the new /bankstatements endpoint.

Find more information in the /bankstatements section.

We deployed two new endpoints for managing your withdrawals: the POST and GET /account/withdrawals/ endpoints, which allow you to create and retrieve all of your withdrawals. The old POST /account/withdraw/ endpoint will be deprecated in the upcoming weeks.

Find more information in the withdrawals section.

We added a small addition to the GET /orders/ endpoint and now return the potential charge associated with the respective order. For orders < 500 â‚Ŧ, a charge of 2â‚Ŧ (20000 as int value in the response) occurs, which we now transparently display. Additionally, we return the "chargeable_at" response element, which is a timestamp informing you about the exact moment in time the charge occured. You can find more information at the orders endpoint.

Please note that in our beta, no charges occur for. When we launched publicly, the charges may occur, depending on the subscription plan you chose.

We just introduced some changes to the way orders are cancelled.
A quick summary:

  • if you want to cancel an order, this works as before via the DELETE /order/{order_id}/ endpoint
  • As soon as you have sent your request, the order status changes to cancelling - this status is for the "intermediary phase", where the stock exchange has not processed the cancel request, yet.
  • The order can either be cancelled by the exchange (order status changes to cancelled) or the cancellation is not possible and the order is executed instead (order status changes to executed).

See here for in-depth information.

We just introduced some changes to the /portfolio endpoint response.
In general, we made the format consistent with our other endpoint, i.e. we output a separate object for each portfolio item in the results array.
Additonally, we added isin_title to the endpoint response.
Here is a sample response:

"results": [
    {
      "space_id": "sp_pyPFYssNNJyV4m8rxtK7LnfGwKLMk2njSv",
      "isin": "US19260Q1076",
      "isin_title": "COINBASE GLOBAL INC.",
      "quantity": 1,
      "buy_quantity": 1,
      "sell_quantity": 0,
      "buy_price_avg": 2965000,
      "buy_price_min": 2965000,
      "buy_price_max": 2965000,
      "buy_price_avg_historical": 2965000,
      "sell_price_min": null,
      "sell_price_max": null,
      "sell_price_avg_historical": null,
      "orders_total": 1,
      "sell_orders_total": 0,
      "buy_orders_total": 1
    },
    {
      "space_id": "sp_pyPFYssNNJyV4m8rxtK7LnfGwKLMk2njSv",
      ...
    }
  ]

Since yesterday we are in Open Beta. 🎉
This means that everyone can now easily register via our website. 😎
We already provide you with a first API Key, which you can use to get started in our Paper Money Environment.
The real money feature is currently tested in a closed beta with a small number of users and will be scaled up step by step 📈
We are looking forward to you and your projects. Tell your friends, too 🤝

We just introduced some changes to the way, pagination works with our APIs. The most important changes:

Pagination in the Trading API

In the Trading API you can paginate with limit and page.

  • With limit you define the number of results per page.
  • With page you can directly access a result page

If you set limit=100 and page=2, the results 101-200 will be displayed.

Pagination in the Market Data API

In the Market Data API, you can also influence your pagination with limit and page.
In addition, the query parameters from and to remain, with which you can specify a time interval for your market data.
If the number of results for the given time interval is > limit, then pagination will occur.