Skip to content

Unknown Integration

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

When you see this

The integration slug in the request path is not addressable on the plane you called. Each plane has its own closed set: a platform-plane caller may address the integrations with platform-visible entity types, and a tenant-plane caller may address only integrations that are not platform-administered and expose a disclosed governance family. A platform-administered integration receives exactly the same body on the tenant plane as a nonsense slug does, so the two cannot be told apart.

Common Causes

  • The slug is misspelled or does not exist.
  • The slug names a platform-administered integration and the request was made on the tenant plane.
  • The slug names an integration whose entity types are not visible on the plane addressed.

Response Example

{
  "type": "https://docs.ankatech.co/errors/unknown-integration",
  "title": "Unknown Integration",
  "status": 404,
  "detail": "Unknown integration: obserability-export",
  "instance": "/api/v3/audit/platform/integrations/obserability-export/events",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

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

How to Resolve

  1. Check the slug in the detail — it is your own value, echoed back bounded and sanitised. The response never lists the acceptable slugs, because that would turn one 404 into an inventory of the deployment's integration surfaces.
  2. If you are on the tenant plane, confirm the integration is one a tenant may address at all; platform-administered integrations are reachable only from the platform plane.
  3. Consult the published integration reference for the slug vocabulary rather than probing this endpoint for it.

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