Skip to content

Invalid Operation Name

URI: https://docs.ankatech.co/errors/invalid-operation-name
HTTP Status: 400 Bad Request

When you see this

The operation name supplied in the request is not a recognized cryptographic operation.

Common Causes

  • A typo in the operation name (for example encypt instead of encrypt).
  • Using an operation identifier the API does not define.
  • Sending an empty or null operation value.

Response Example

{
  "type": "https://docs.ankatech.co/errors/invalid-operation-name",
  "title": "Invalid Operation Name",
  "status": 400,
  "detail": "Operation name 'encypt' is not recognized. Valid operations: encrypt, decrypt, sign, verify.",
  "instance": "/api/v3/admin/keys/my-mlkem-key/operations",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

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

How to Resolve

  1. Use one of the recognized operation names: encrypt, decrypt, sign, verify (and their documented variants).
  2. Check spelling and case against the Developer Hub Reference.
  3. Re-submit with a valid operation name.

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