Skip to content

idempotency_key_reused

Idempotency-Key reused with a different request

BetaAPI v2 is in public beta: endpoints, fields and behaviour can change before general availability. See the changelog

Last updated

Idempotency-Key reused with a different request

Section titled “Idempotency-Key reused with a different request”

Code: idempotency_key_reused · HTTP status: usually 422

The Idempotency-Key header was already used for a request with a different method, path or body. Keys are remembered for 1 hour.

Send a new Idempotency-Key for a new request. Reuse a key only to retry the identical request.

{
"code": "idempotency_key_reused",
"type": "https://docs.stoqapp.com/v2/docs/api-v2/errors/idempotency-key-reused/",
"title": "Idempotency-Key reused with a different request",
"status": 422,
"detail": "This Idempotency-Key was already used for a different request. Send a new Idempotency-Key for a new request. Reuse a key only to retry the identical request.",
"errors": [
"This Idempotency-Key was already used for a different request"
],
"details": [
{
"code": "idempotency_key_reused",
"message": "This Idempotency-Key was already used for a different request",
"path": null,
"value": null,
"expected": null
}
]
}

Every API v2 and MCP failure carries code and a type link to its page here. See Errors & Responses for the full envelope.

Was this page helpful?

Still stuck? Ask Quinn or chat with support