RocketKOR supports idempotent API calls for transactions and card issuing. This means that making multiple identical requests has the same effect as making a single request.
The request must include a unique idempotency key. This key identifies the request and ensures that the request can be retried, if necessary, without creating a duplicate request. 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 request.
RocketKOR does not validate that idempotency keys are unique when requests are submitted. RocketKOR checks the idempotency keys in requests made in the past 24 hours to determine if these keys already exist for previous requests. If a duplicate key is found in a previous request, the request details are returned.
In supported APIs, 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, with a minimum length of 6 characters and a maximum length of 255 characters.
Key points to remember when using idempotency keys: