idempotency_conflict (409)
Public API Problem code idempotency_conflict — same Idempotency-Key reused with a different JSON body (HTTP 409).
idempotency_conflict (409)
type: https://docs.inboxops.app/api/problems/idempotency_conflict
For ticket create (POST /api/v1/tickets), the same Idempotency-Key was sent again with a different JSON body than the first successful request stored under that key.
What to do: Use a new idempotency key if you intend a different create, or replay the exact same body to get the same 201 response as the original. See Public API (Idempotency).
Related
- Conflict — business rule duplicates (tags, companies)
- Public API errors overview
Was this page helpful?
Last updated 3 weeks ago
Built with Documentation.AI