Skip to main content

License acquisition error codes

If the DRM Cloud service can't produce a license response, the error is indicated by an HTTP status code in the 4xx or 5xx range. The body of the response contains a JSON object with more details about the error, for example:

{
"code": "drm_3032",
"status": 403,
"message": "Token signature invalid",
"requestId": "c42e3599-3a47-4ed1-ad72-79a5b2a26b71"
}
HTTP statusCode in JSON responseDescription
403drm_4002The payload of the license request is missing
403drm_4003The payload of the license could not be parsed
403drm_4005BrandGuid is invalid or configuration is missing
403drm_3030The license was denied because the JWT token does not allow a license to be issued for this request (because of IP or KeyId restrictions)
403drm_3031The JWT token or access_token is invalid or has expired
403drm_3032The signature of the DRM token is invalid
403drm_3033The KeyID in the DRM token could not be matched
403drm_3034The IP address in the DRM token could not be matched
403drm_3035Failed to decrypt the DRM token
403drm_3036The UserToken is not valid
403drm_3037The DRM token could not be properly validated
403drm_3038The frontend signature validation failed
403drm_3039The one-time token (nonce) has already been used
403drm_3100License server error
500common_3Internal server error