Skip to content

Invalid Delivery Provider Target

URI: https://docs.ankatech.co/errors/invalid-notification-target
HTTP Status: 422 Unprocessable Entity

When you see this

The ROOT platform tenant was named as the target of a per-tenant delivery-provider write. The ROOT tenant has no per-tenant delivery chain, because its chain is the deployment plane — reached through the platform notification endpoints instead. The refusal runs after the caller gate and the tenant existence probe and before any work, so no provider row is written and no audit row is emitted.

Common Causes

  • Using the ROOT tenant's id in the tenant path of a platform-operated per-tenant delivery-provider write.
  • Intending to change the deployment's own delivery chain and reaching for the per-tenant surface to do it.

Response Example

{
  "type": "https://docs.ankatech.co/errors/invalid-notification-target",
  "title": "Invalid Delivery Provider Target",
  "status": 422,
  "detail": "The ROOT platform tenant is not a valid target for a per-tenant delivery provider; its chain is the deployment plane",
  "instance": "/api/v3/admin/platform/tenants/00000000-0000-0000-0000-000000000001/notification/providers",
  "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. To change the deployment's delivery chain, use the platform notification-provider endpoints under /api/v3/admin/platform/notification/providers.
  2. To configure a customer tenant's own chain, put that tenant's id in the path — not the ROOT platform tenant's.
  3. This is not a secret-custody refusal; nothing about credential custody needs checking.

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