Skip to content

License Deployment Mismatch

URI: https://docs.ankatech.co/errors/license-deployment-mismatch
HTTP Status: 422 Unprocessable Entity

When you see this

The license artifact is valid but was issued for a different deployment than the one presenting it. Licenses are bound to a specific deployment.

Common Causes

  • Using a license issued for one deployment on a different deployment.
  • A deployment identifier that does not match the one the license was signed for.
  • Reusing a license artifact across environments.

Response Example

{
  "type": "https://docs.ankatech.co/errors/license-deployment-mismatch",
  "title": "License Deployment Mismatch",
  "status": 422,
  "detail": "The license artifact does not match this deployment.",
  "instance": "/api/v3/licenses/validate",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

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

How to Resolve

  1. Verify the license was issued for this specific deployment.
  2. Obtain a license artifact bound to the correct deployment from ANKATech.
  3. Install the matching license and retry validation.

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