Idempotency - KetaPay Docs

Every POST needs an Idempotency-Key header: any unique string up to 255 characters. A UUID is ideal; your own order or job id works too.

curl https://api.ketapay.com/v1/checkout_sessions \
  -H "Authorization: Bearer $KETAPAY_SECRET_KEY" \
  -H "Idempotency-Key: 5f1c9a2e-8b7d-4c3a-9e6f-2d1b0a9c8e7f" \
  ...

How it works

You send	You get
A new key	The request runs, and its response is stored with the key
The same key and the same body	The stored response, without running the request again
The same key and a different body	`409 idempotency_key_reused`
No key on a `POST`	`400 idempotency_key_missing`

Keys are kept for 24 hours, then the same key can be used again.

When to retry

Retry with the same key after a network error, a timeout, a 429 or any 5xx. If the first attempt went through, you get its response; if it didn’t, it runs now. Either way it happens once. Don’t retry 4xx errors other than 429: fix the request first, and use a new key.

The libraries do it for you

The Node.js, PHP and Laravel libraries add a key to every POST and reuse it on their automatic retries. Pass your own to tie it to your records:

await ketapay.checkoutSessions.create(params, {
  idempotencyKey: `order_${order.id}`,
})