Verification error handling complies with the GS1 Lightweight Messaging Standard for DSCSA Verification of Product Identifiers, Release 1.3.
The information in the following tables is taken from the document Implementation Guideline - GS1 Lightweight Messaging Standard for DSCSA Verification of Product Identifiers, Release 1.3.
HTTP Status Code Responses
| HTTP Status Code Response | Description |
|---|---|
| 200 | A response code of 200 means the request was successful and details about the response can be found in the body of the response. Only a 200 response will issue a JSON payload. |
| 400 | Bad Request. The request was not formatted properly. |
| 401 | Unauthorized. The request was not allowed because the request did not pass authentication. |
| 403 | Forbidden. The request was valid, but the server is refusing to provide a response because the Requestor lacks permission. When ATP verifiable credential is provided in the header, the credential is expired, revoked, or contains an invalid signature. |
| 404 | Not found. GTIN may be missing in the Lookup Directory/Resolver or has an expired GTIN record in the Lookup Directory. |
| 405 | Method Not Allowed. The request method is not supported. |
| 408 | Request Timeout. The server timed out waiting for the request. |
| 500 | Internal Server Error. System failed to process the request because of an error inside the system. |
| 502 | Bad Gateway. The server was acting as a gateway or proxy and received an invalid response from the upstream server. Indicates that one server tried to use another VRS system and that system was down. |
| 503 | Service Unavailable. System is undergoing maintenance or is otherwise temporarily unavailable for API queries. |
| 504 | Gateway Timeout. The server, while acting as a gateway or proxy, performed multiple retries but did not receive a timely response from the upstream server specified by the URI (for example, HTTP, FTP, LDAP) or some auxiliary server (for example DNS) it needed to access in attempting to complete the request. |
Potential Resolution Paths for HTTP Status Code Responses
| HTTP Status Code Response | Suggested Resolution |
|---|---|
| 200 | None |
| 400 | Check that the request conforms to the specification, and re-issue the request in the correct format. |
| 401 | Check and obtain necessary authentication credentials. |
| 403 | Check and obtain necessary permission and credentials. When ATP verifiable credential is provided in the header, resolve your credential issue, and resubmit the request. |
| 404 | Check URI format and correct resource paths and names. Contact Mfg. to confirm the GTIN exists. Contact verification service provider to ensure Lookup Directory is synchronized. |
| 405 | Check and correct method names and parameters. |
| 408 | Re-try sending the request to the server. If timeout continues, check connectivity request to server and contact verification service provider. |
| 500 | Contact Verification Service Provider (Movilitas.Cloud). |
| 502 | Re-try sending the request to the server. Note that re-try could be limited to the credential presentation expiration. If timeout continues, check connectivity request to server and contact verification service provider. |
| 503 | Re-try sending the request to the server. Note that re-try could be limited to the credential presentation expiration. If timeout continues, check connectivity request to server and contact verification service provider. |
| 504 | Re-try sending the request to the server. Note that re-try could be limited to the credential presentation expiration. If timeout continues, check connectivity request to server and contact verification service provider. |
