License Expired
URI: https://docs.ankatech.co/errors/license-expired
HTTP Status: 422 Unprocessable Entity
When you see this
The license artifact has passed its validity period and is no longer accepted.
Common Causes
- A license whose expiration date has passed.
- Continuing to use a license beyond its term.
- A clock or term mismatch that places the deployment outside the license validity window.
Response Example
{
"type": "https://docs.ankatech.co/errors/license-expired",
"title": "License expired",
"status": 422,
"detail": "The license artifact is past its validity period and grace window.",
"instance": "/api/v3/admin/platform/license/import",
"extensions": { "requestId": "8b0c2d4e-6f1a-4b3c-9d5e-2a7f8c1b0d3e" }
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
Raised by the License Server, relayed by the Admin API
The import is POST /api/v3/admin/platform/license/import on the Admin API, which forwards the artifact to the licence server over a service-to-service call; the licence server is the only validator of the artifact and raises this refusal. The Admin API relays its type, title, detail and status unchanged and sets its own instance and extensions.requestId. Correlate a request by extensions.requestId.
This refusal is about the artifact, not about a running deployment
It is raised while importing a license artifact that is already past its term. A deployment whose license lapses while it is running is a different condition with a different type and status: Deployment License Expired, 402.
How to Resolve
- Confirm the license expiration date and the deployment's current date.
- Renew the license with ANKATech and install the new artifact.
- Contact your account manager to arrange renewal if the license has lapsed.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.