Idempotency and retries
Send an Idempotency-Key with every write so a retry never acts twice.
Networks fail halfway. An Idempotency-Key makes a write safe to send again.
Idempotency-Key: shortlist-app_123-2026-11-07- 8 to 128 characters: letters, digits,
.,_,:and-. - The same key with the same body returns the first result, for as long as Invyte keeps the action.
- The same key with a different body is refused with
409 conflict. - Use one key per intended action. A key built from your own ids (
invite-prospect_42-job_7) makes retries natural.
Reads don't need a key. Writes from API keys and agents must send one; people's AI clients get one from the MCP server.
What to retry
| Response | Retry? |
|---|---|
| Network error or timeout | Yes, same key and body. |
429 rate_limited | Yes, after Retry-After seconds. |
503 temporarily_unavailable | Yes, with backoff. |
409 conflict | No. Fix the input or start again with a new key. |
| Any other 4xx | No. |