Skip to main content

Handling errors

Errors structure and errors handling approach is the same for all TEOS Platform APIs. Please, refer to Handling errors for the info about handling errors received from TMS API.

1xxxx codes​

Error codes 1xxxx indicate non-business logic related issues with input (auth issues, issues with parsing input data, rate limiting etc.). These errors are mostly 'technical', related to the problems in the API consumer's code.

12000 / 12001​

MessageThere were OData validation errors
Descriptionmalformed oData request (missing required fields, redundant fields etc.)
Detailscontains the array of sub-errors, specifying the issue
What to do
  • check the correctness of the request body according to oData and the request specs.
  • check the details field for additional information

13000​

MessageWhoa! Calm down, cowboy! Quota exceeded
Descriptionrequests quota for the tenant per 30 days was exceeded
Detailscontains the details about the current quota, time to wait until requests are allowed again
What to do
  • wait until the requests are allowed again
  • check why the quota was exceeded
  • if you want to change the quota, contact your CL manager

2xxxx codes​

Error codes 2xxxx indicate business logic related issues with input (failed preconditions, validations etc.).

22000-2002​

MessageUser with id = userId already exists
DescriptionYou're trying to register a new user with existing user id
What to doCheck that correct user in requesting the operation
Try again with the correct user. If it doesn't help, contact support

22000-2003​

MessageIncorrect time zone id: timeZoneId
DescriptionYou're trying to register a new user with incorrect timeZoneId
What to doTry again with the correct timeZoneId format according to api description

22000-2004​

MessageIncorrect language code: languageCode
DescriptionYou're trying to register a languageCode which is not supported by TEOS Platform
What to doTry again with the correct languageCode according to api description