Skip to main content

idempotency-key-too-long

Type URI: https://developer.risepeople.com/errors/idempotency-key-too-long HTTP status: 400 Bad Request Format: application/problem+json (RFC 7807)

When this fires​

The Idempotency-Key header you sent is longer than the 256-character maximum. Long keys waste cache memory and almost always indicate a client error (e.g. accidentally serializing the request body into the key).

Example response​

{
  "type":   "https://developer.risepeople.com/errors/idempotency-key-too-long",
  "title":  "Idempotency Key Too Long",
  "status": 400,
  "detail": "Idempotency-Key must be 256 characters or fewer.",
  "instance": "/v1/payroll/runs"
}

How to fix it​

Use a short, opaque, high-entropy identifier for Idempotency-Key. The conventional choice is a UUIDv4:

Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

UUIDs are 36 characters — well under the limit and effectively collision-free across the 24-hour cache window. Don't put any user data, hashes of the request body, or timestamps into the key — it's an arbitrary correlation token, not a content signature.