Idempotent Requests

Introduction

Some API endpoints support idempotency for retrying requests without the risk of performing the same operation multiple times. Idempotency is crucial for safeguarding the customer against clicking a button several times in your UI (e.g. due to unresponsive UI) and initializing duplicate transactions.

How to fulfil idempotency

In our API interface, if a request to create a payout is successfully sent to the server, but you did not receive a response due to a network error, you can retry the same request with the same idempotency key to ensure that only one payout is created.

To perform an idempotent request, you can provide an additional idempotency-key header in the request. You can decide how you create unique keys, but we recommend using V4 UUIDs to avoid possible duplicates. The parameters of a request with the same idempotency key should not change, otherwise a IDEMPOTENCY_KEY_ALREADY_USED error will be returned.

Idempotent requests are valid for 24 hours, i.e. all requests to an endpoint made within 24 hours with the same Idempotency key and request body will be treated as the same request, and return the already created object.

These POST requests accept idempotency keys:

Create Merchant

Update Merchant

Create Buyer

Update Buyer

Create Fiat Withdrawal

Create Conversion

Introduction#

How to fulfil idempotency#

Introduction

How to fulfil idempotency