Skip to main content

Errors

This page covers the authorization errors common to every Xemelgo GraphQL API. Errors specific to an individual operation (for example, a duplicate tracker serial on create) are documented on that operation's page.

Authorization Errors​

These are returned by the GraphQL APIs when the Authorization header is missing, malformed, or expired. See Authentication for how to obtain a valid IdToken.

ErrorError codeException
Expired token401Unauthorized
Invalid token401Unauthorized
Missing Authorization Header401Unauthorized

Error Response Examples​

Expired Token​

{
"errors": [
{
"errorType": "UnauthorizedException",
"message": "Token has expired."
}
]
}

Invalid Token​

{
"errors": [
{
"errorType": "UnauthorizedException",
"message": "Unable to parse JWT token"
}
]
}

Missing Authorization Header​

{
"errors": [
{
"errorType": "UnauthorizedException",
"message": "User is not authorized to make this call."
}
]
}

Operation Errors​

Most GraphQL operations report business-level failures with an HTTP 200 status: the failure detail is carried in the response errors array, usually alongside a partial data payload (for example, inventoryIds: [] when nothing was created). Always inspect the errors array even on a 200 response. Structurally invalid requests (malformed body, missing required GraphQL arguments) are rejected earlier with a 400.

Each entry in errors has an errorType, a human-readable message, and the path of the field that failed. The common types:

errorTypeWhen it occursHTTP
PayloadValidationErrorThe request payload is invalid — e.g. a duplicate id or trackerSerial within the same request.200
ResourceAlreadyExistErrorA unique value already exists — e.g. a trackerSerial already attached to another item.200
ResourceNotFoundErrorA referenced record does not exist — e.g. ids passed to an update/delete that aren't found.200
FilterErrorA filter expression could not be parsed.200
MalformedHttpRequestExceptionThe request is structurally invalid or missing required GraphQL arguments.400

Error Response Examples​

PayloadValidationError — duplicate value in payload
{
"data": {
"createInventory": {
"inventoryIds": []
}
},
"errors": [
{
"path": ["createInventory"],
"data": null,
"errorType": "PayloadValidationError",
"errorInfo": null,
"message": "Duplicate value [12345679] found in the 'trackerSerial' property. Please make sure each item has a unique trackerSerial."
}
]
}
ResourceAlreadyExistError — value already in use
{
"data": {
"createInventory": {
"inventoryIds": []
}
},
"errors": [
{
"path": ["createInventory"],
"data": null,
"errorType": "ResourceAlreadyExistError",
"errorInfo": null,
"message": "Item '1234' has tracker serial '12345679' that already exists. Use 'reuseTrackerSerial' if you want to reuse this tracker serial."
}
]
}
ResourceNotFoundError — referenced records not found
{
"data": {
"updateAssets": {
"assets": []
}
},
"errors": [
{
"path": ["updateAssets"],
"data": null,
"errorType": "ResourceNotFoundError",
"errorInfo": null,
"message": "Assets not found: Asset-BIN-02, Asset-BIN-03"
}
]
}
FilterError — invalid filter expression
{
"data": {
"inventory": null
},
"errors": [
{
"path": ["inventory"],
"data": null,
"errorType": "FilterError",
"errorInfo": null,
"message": "Error: Lexical error on line 1. Unrecognized text.\n\tid === \"1234\""
}
]
}