Skip to main content

Idempotency key for transactions

You can now send an idempotency key when creating transactions. It ensures that the same transaction is not recorded twice, for example, when a request is retried after a network failure or a timeout.

The Create Transaction endpoint accepts the optional idempotency-key header: a unique identifier for the transaction, generated by your system (such as a UUID or the operation's code in your database).

  • The key is unique per portfolio. The same key can be used in different portfolios.
  • If the request is sent with a key already used in the portfolio, the transaction is not created and the API responds with an HTTP 409 Conflict error (idempotency key already used).
  • Without the header, each request creates a new transaction, even if the data is identical.

Learn more in Transaction.