Skip to content

Composite Component Algorithm Mismatch

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

When you see this

A component algorithm in the composite message does not match the corresponding component algorithm declared by the composite key, so the operation cannot proceed.

Common Causes

  • Processing a composite message whose component algorithm differs from the key's component.
  • Using a composite key whose component algorithms were changed after the message was produced.
  • Pairing component values that belong to incompatible composite definitions.

Response Example

{
  "type": "https://docs.ankatech.co/errors/composite-component-algorithm-mismatch",
  "title": "Composite Component Algorithm Mismatch",
  "status": 422,
  "detail": "A composite component algorithm does not match the key definition.",
  "instance": "/api/v3/crypto/verify",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

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

How to Resolve

  1. Verify the composite key's component algorithms match those used to produce the message.
  2. Use the exact composite key (and version) that created the message.
  3. Re-create the message with matching component algorithms, or select the correct key, then re-submit.

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