Every time you want to send out a gift through Glede you need to create an order for it.
Send an Idempotency-Key for every logical order and reuse that key with the
same JSON body on retries, including after a timeout. A completed retry
returns the original 201 response, order ID and gift links without creating
another order or drawing funds again. Object property order does not matter;
array order and field values do. Keys are scoped to the authenticated business,
including across API key rotation, and are retained without automatic expiry.
Reusing a key with a different body returns 409. A concurrent request, or a
request whose outcome is uncertain after a failure, also returns 409. Retry
with the same key and body; if the conflict persists, contact support with
the reference in the error. Do not switch keys to bypass a conflict: the first
request may already have drawn funds or created the order. A request that is
rejected before any funds are drawn or the order is saved (for example an
unknown template or funding source, or missing invoice details) releases its
key: fix the cause and retry with the same key and body. Errors after that
point keep the key reserved until reconciled. A replay is the original
response, not a fresh view of an order that may since have been approved or
refunded.
The header is optional for backwards compatibility. Without it, every request
creates a new order; identical bodies and invoice references are not deduplicated.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||

