Composite Wire Shape Mismatch

URI: https://docs.ankatech.co/errors/composite-wire-shape-mismatch
HTTP Status: 422 Unprocessable Entity

When you see this

The composite (hybrid) cryptographic message you supplied does not match the wire shape the operation expects — for example the number or ordering of component values does not align with the composite key definition.

Common Causes

• Submitting a composite ciphertext or signature whose component layout differs from the key's definition.
• Mixing component values from different composite keys.
• A serialization that does not preserve the expected composite structure.

Response Example

{
  "type": "https://docs.ankatech.co/errors/composite-wire-shape-mismatch",
  "title": "Composite Wire Shape Mismatch",
  "status": 422,
  "detail": "The composite message wire shape does not match the expected structure for this key.",
  "instance": "/api/v3/crypto/decrypt",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

Content-Type: application/problem+json — the response follows RFC 7807 Problem Details.

How to Resolve

1. Confirm the composite message was produced with the same composite key definition you are using to process it.
2. Do not reorder, drop, or substitute component values within a composite message.
3. Regenerate the composite message with a compliant serialization and re-submit.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.