Skip to main content
- Safe retries

API idempotency

Every non-GET request needs an Idempotency-Key header. Use one stable key per logical write so network retries are safe.

Last updated - June 5, 2026 Read time - 4 min Author -

Required on writes

Send Idempotency-Key on every POST, PUT, PATCH, and DELETE request. Missing keys return 400 idempotency_key_required.

Idempotency-Key: order-5501234567890-assignment-1

Replay behavior

  • Same key, same endpoint, same body: the API replays the successful response and does not write again.
  • Same key with a different body: the API returns 409 idempotency_conflict.
  • Same key while the first request is still running: the API returns 409 idempotency_conflict_in_progress.
  • Keys expire after 24 hours. Generate a new key for a new logical operation.

API docs

Start here

API quickstart

Ping the API, import an asset, map it to a product, and assign access to an order.

 Reference

Endpoint reference

Review the available endpoints for assets, mappings, orders, access changes, and status.

Was this helpful?

Still stuck? Email admin@alvaapps.com.

Last updated 2026-06-05