Idempotency
Safely retry supported POST requests without creating duplicate work.
Idempotency
Use Idempotency-Key on supported non-streaming POST requests:
POST /v1/conversationsPOST /v1/messagesPOST /v1/conversations/{conversationId}/messages
Behavior
- Matching retries replay the original completed response
- Reusing a key with a different request body returns
409 idempotency_conflict - Streaming requests do not support
Idempotency-Key
Header format
Use any stable string from your system, such as a request UUID or a composite key that combines user ID and message ID.