Concepts
Idempotency
Why a retry can never pay twice.
Networks fail. Every write in the Speedy system is safe to repeat, and the same rule applies to you.
On payouts to you
Our transfer id is sent as idempotencyKey on every create-payout request. You must return the same partnerRef for the same key, however many times it is sent.
On calls to the Speedy API
Requests that create something require an Idempotency-Key header of 8 to 200 characters: letters, digits and . _ : -
POST /v1/transfers
Idempotency-Key: 5d1c9a52-7e0b-4c2a-8f63-2b7f6a1e9d04
Content-Type: application/json| Situation | Result |
|---|---|
| Same key, same request | The original result is returned. Nothing happens twice. |
| Same key, different request | 422 idempotency_key_reused. |
| No key on a request that needs one | 400 idempotency_key_required. |