Idempotent requests

Apps can retry a write safely. Send an Idempotency-Key header and a repeat of the same request returns the first response instead of doing the work twice.

When it applies

Requests made with an app's OAuth token (inka_…). Secret-key requests aren't covered; use a unique reference_id instead.
POST, PUT and DELETE.
Keys of 8 to 255 characters. A UUID works well.

A key belongs to your app and the merchant the token acts for, and lasts 24 hours.

What happens on a repeat

You send	You get
The same key and body	The first response again, with the header `idempotency-replay: true`.
The same key with a different body	`409` `idempotency_key_reuse_with_different_payload`.
The same key while the first is still running	`409` `request_in_progress`. Wait and retry.

PreviousErrors NextLists and filters

curl https://api-dev.inkress.com/api/v1/orders \ -H "Authorization: Bearer MERCHANT_ACCESS_TOKEN" \ -H "Idempotency-Key: 6b1f0c2e-6c1d-4c55-9a3e-1042" \ -H "Content-Type: application/json" \ -d '{ "reference_id": "order_1042", "kind": "online", "total": 2500, "currency_code": "JMD", "title": "Order 1042", "customer": { "email": "tanya@example.com", "first_name": "Tanya", "last_name": "Clarke" }, "meta_data": { "return_url": "https://kloset.shop/thanks" } }'

{ "state": "ok", "result": { "id": 88214, "reference_id": "order_1042", "title": "Order 1042", "status": 1, "total": 2500, "currency": "JMD", "customer": { "first_name": "Tanya", "last_name": "Clarke", "email": "tanya@example.com" }, "merchant": { "name": "Kingston Kloset", "username": "kingston-kloset" }, "payment_urls": { "payment_url": "https://inkress.com/pay/…", "short_link": "https://ink.rs/4Fq2", "qr_url": "https://inkress.com/qr/…" }, "invoice_url": "https://inkress.com/invoice/…", "meta_data": { "return_url": "https://kloset.shop/thanks" }, "created_at": "2026-10-07T15:42:10Z" } }