Learn  /  About Idempotent Transaction Calls

About Idempotent Transaction Calls

What Are Idempotent Calls?

RocketKOR supports idempotent API calls when creating a transaction. This means that making multiple identical requests has the same effect as making a single request.

A transaction creation request must include a unique idempotency key that identifies the transaction. This ensures that the request can be retried, if necessary, without creating a duplicate transaction. For example, if a request is disrupted due to a failed connection, you can retry the request using the same idempotency key. Using the same key ensures that the subsequent request will not result in a new, duplicate transaction.

RocketKOR does not validate that idempotency keys are unique when requests are submitted. RocketKOR does check the idempotency keys in requests made in the past 24 hours to determine if these keys already exist for previous transactions.

How Do I Make an Idempotent Transaction Call?

The idempotency key is provided in an Idempotency-Key: <key> request header. You can use a v4 UUID or any other unique string for the key.

Key points to remember when using idempotency keys:

  • Always inlude an idempotency key in a transaction request. Requests without an idempotency key may result in duplicate data creation if the request is retried.
  • Ensure the idempotency key is unique. Accidentally supplying the same idempotency key in different transaction requests may result errors and prevent data creation.