Error Messages

Owned by Jo Burrell (Unlicensed)
Last updated: Mar 11, 2022 by Steven Baker (Unlicensed)
1 min read

Authentication Errors

  • 401 - Invalid X-Authorization header - caused by signature not formatted correctly and/or API Key invalid.

  • 401 - No X-Authorization header provided and/or missing entirely.

  • 401 - Request outside of boundaries of XXXX and XXXX - the signature and X-Date header is outside the 20 second boundary with our service.

  • 401 - Unknown user from X-UserID - Client sent an invalid UserID.

Other Errors

  • 403 - Blocked by our WAF. This is typically from outside Australia access. If you are getting this error, please contact our support to investigate your access and whether this is incorrectly classified as outside Australia.

Request Errors

  • 429 - Too Many Requests - too many requests on the user ID per second. Currently 100 per second.

  • Remote username not provided - Missing the remote user ID in the payload.

  • Remote username too long - Remote user ID in the request is longer than 255 characters.

  • responseCode of “unavailable” in match fields result - attempted to match against a dataset not available to this client.

  • responseCode of “insufficientFields” in match fields result - attempted to match against a dataset without all the required fields being populated.

 

Do errors count against transaction quotas?

Errors on the single match service are not counted against the quota.

If you are using bulk matching and an error occurs mid the bulk matching due to a malformed file or missing fields, then the records that were matched without errors (before the error occurred) would count against your quota.