Skip to content

Resource Not Found

URI: https://docs.ankatech.co/errors/not-found
HTTP Status: 404 Not Found

When you see this

The server could not find the resource you requested. This generally means the identifier (e.g. a key ID, endpoint, or path parameter) does not exist or has been removed.

Common Causes

  • You supplied an incorrect or misspelled identifier in the URL path (e.g. wrong kid).
  • You attempted to fetch a resource that was deleted or never created.
  • You called an endpoint that does not exist (typo in the path or wrong HTTP method).
  • The resource exists in a different context or namespace than the one you used.

Response Example

{
  "type": "https://docs.ankatech.co/errors/not-found",
  "title": "Resource Not Found",
  "status": 404,
  "detail": "No key with the requested identifier exists in this tenant.",
  "instance": "/api/v3/admin/tenants/2f1c9d84-6b2e-4d3a-9f57-0a1b2c3d4e5f/keys/my-mlkem-key",
  "timestamp": 1751500800,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 7807 Problem Details. The example above is an Admin API body, where the correlation identity is extensions.requestId; the Core API and the PQC Handshake API instead emit a top-level correlationId. Read the member your service emits — see Error Index & Overview.

instance is always the path of the request you made. A 404 raised by an internal upstream service never republishes that service's own route — see S2S Relay Envelope.

How to Resolve

  1. Verify the URI you are calling and ensure path parameters (IDs, names) are correct.
  2. If you expect the resource to exist, confirm via your client (e.g. use GET /api/keys to list available keys).
  3. For endpoints, check the interactive Developer Hub Reference to confirm the correct path and method.
  4. If you deleted the resource intentionally, no further action is required; otherwise, recreate it as needed.

If you continue to receive a 404 after these steps, please consult the full API reference at
Developer Hub Reference or contact support.