The following are error Data Graph API will return the following error codes in case of
any error:
| Error Code | Description |
|---|---|
| DIS-1001 | Invalid token |
| DIS-1002 | Not Authorized to access this API |
| DIS-1003 | Issue with internal services |
| DIS-1004 | Workspace Id is missing from Bearer Token |
Operation errors
Below are the types of errors that can occur when an operation is attempted:
- Syntax errors (for example, a query was malformed)
- Validation errors (for example, a query included a schema field that doesn't exist)
HTTP status codes
Data Graph API supports multiple HTTP status codes for a POST request based on the response.
- 206: When a page number does not exist, you will see an error and the
data. Below is a sample for an error occurred if the requested page does not exist:
{ "errors": [ { "detail": "Requested page does not exist.", "code": "DIS-DG-1010" } ], "data": { "getById": { "addresses": { "data": [ { "addressNumber": "5500" } ] }, "parcels": null } }, "id": "79110ecfbe74c1457b5b15471c41470f" } - 400: When request is invalid or required attributes are not given:
{ "id": "89ea65799219ddbb0636006a71641382", "errors": [ { "code": "DIS-DG-1000", "detail": "Request is not valid" } ] } - 500: When complete request fails because of an internal server
error:
{ "errors": [ { "code": "UNKNOWN_ERROR", "detail": "Exception while fetching data (/getById/addresses) : issues with internal services. Please try again later" } ], "id": "809b75f8-b5bf-43f5-81a4-5c7791d86753" } - Error is returned in case of invalid page number passed for an entity:
{ "errors": [ { "detail": "Requested page does not exist.", "code": "DIS-DG-1010" } ], "id": "c6151d1ec59a98e470962f624192a513" } - Error schema is inline with other Data Integrity Suite APIs:
{ "id": "1e816e3f697627bb3689459d3303dbf8", "errors": [ { "code": "DIS-DG-1000", "detail": "Request is not valid" } ] }