Skip to content

Unknown Error Type

URI: https://docs.ankatech.co/errors/unknown-error-type
HTTP Status: 404 Not Found

When you see this

You are here because you followed an error link — from the admin console, from an API client, or from a type member in a problem+json response body — and the reference page for that error type has not been published.

This is not an error returned by the API. No AnkaSecure service emits https://docs.ankatech.co/errors/unknown-error-type in a type member; it is the documentation site's answer when the address you followed names an error type it does not document. The response carries an honest 404 status: the page really is not there.

What this means for the failure you were investigating

Nothing about the failure changes. The response you received is complete on its own, and every member you need is in it:

  • title — a short, human-readable summary of the failure.
  • detail — what specifically went wrong in your request.
  • status — the HTTP status class, which tells you whether to retry, correct the request, or escalate.
  • instance — the path of the request you made.
  • the correlation identifier — top-level correlationId in the Core API and the PQC Handshake API, extensions.requestId in the Admin API and the Audit API, and the X-Correlation-Id response header from the Auth API and the License Server. See Error Index & Overview.

The missing page would have added common causes and resolution steps. It would not have added facts about your request that the body does not already carry.

How to Resolve

  1. Read the detail member of the response body — it is written for the specific failure.
  2. Look the type up in the Quick Reference Table on Error Index & Overview. It carries every published error page, keyed by status class, so a closely related type is often documented even when this exact one is not.
  3. For endpoint-level schemas and examples, see the Developer Hub Reference.
  4. If you need the page itself, contact support with the error type shown above and the correlation identifier from the response. The reference is published from the same source as the API, so a missing page is reported and filled rather than worked around.

A missing reference page never hides a failure. The problem+json body is the authoritative account of what happened; this reference explains it in more depth where a page exists.