Delivery Providers Not Included In This Edition
URI: https://docs.ankatech.co/errors/notification-not-entitled
HTTP Status: 403 Forbidden
When you see this
A tenant tried to configure its own delivery providers without the edition that includes that capability. The caller is inside its own tenant boundary and holds the scope — what it lacks is a commercial entitlement, so more permissions will not lift the refusal. Notifications for the tenant still leave normally: without the entitlement the tenant inherits the deployment's delivery chain.
Common Causes
- The tenant's effective edition does not include tenant-configured delivery providers.
- Calling
declare,replace,testorenableon the tenant notification-provider surface without the entitlement. Reads,disableandvalidateare deliberately not gated.
Response Example
{
"type": "https://docs.ankatech.co/errors/notification-not-entitled",
"title": "Delivery Providers Not Included In This Edition",
"status": 403,
"detail": "Configuring your own delivery providers is included in the Enterprise edition. Your notifications are delivered through the platform's providers in the meantime. Contact your account manager to enable it for this tenant.",
"instance": "/api/v3/admin/tenants/9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d/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
- Contact your account manager to enable tenant-configured delivery providers for this tenant. The capability is included in the Enterprise edition.
- In the meantime, notifications for this tenant are delivered through the platform's own providers; nothing is failing to send.
- If you only need to switch an already-active provider off, use
disable— it is not gated, so a tenant can always reduce its own exposure.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.