Skip to main content
All write operations in the Guppy API support idempotency keys. This allows you to safely retry requests without accidentally creating duplicate intents or payments.

​
Using Idempotency Keys

Include an Idempotency-Key header with a unique string for each request. 
Idempotency-Key: <unique_string>
If a request with the same key is received, Guppy will return the same response as the first successful request.

​
Best Practices

  • Generate a new idempotency key per logical operation (e.g., “create intent”).
  • Reuse the same key when retrying the same operation due to timeouts or transient errors.
  • Store the key server-side for at least 24 hours so your own retries remain consistent.
  • If you accidentally reuse a key for a different operation, Guppy may return 409 Conflict.