Possible errors when requesting an API
When a consumer calls the API you have enabled, several errors can occur.
After enabling an API for a dataset, authorized consumers can start requesting the API. In the Activity tile of the API tab, you can check if the requests failed or were successful. The last 10 errors of the last 24 hours are displayed.
| Error message | Error code | HTTP status | Additional information |
|---|---|---|---|
| Authorization header is absent from the request | NO_AUTHENTICATION | 401 | The header does not include login and password information. |
| API key is invalid | INVALID_AUTHENTICATION_FORMAT | 401 | The request header has been sent with the right information, but in the wrong format. |
| Invalid credentials | INVALID_AUTHENTICATION_VALUE | 401 | There is no corresponding consumer for the request, even in the right format and with the right information. |
| Unsupported functionality | NOT_IMPLEMENTED | 501 | The request is trying to use a method or functionality that is not supported. |
| Entity does not exist | NOT_FOUND | 404 | The API call is trying to request a value or id that does not exist in the dataset. |
| Unknown server error | UNCAUGHT_ERROR | 500 | Unknown error. Retry the operation later. |
| Entity is not unique | ENTITY_NOT_UNIQUE | 500 | The request is calling an id or value that is duplicated in the source data. See with the user who created the dataset in order to fix the source data. |
| Request timeout | TIMED_OUT | 408 | The request took too long to complete. Retry the operation later. |
| Unsupported Talend Entity API error | UNSUPPORTED_TEA_ERROR | 500 | Issue with the Remote Engine or OData compatibility. Contact the Remote Engine admin or Talend Support. |
| Unsupported Talend Entity API error | UNCAUGHT_TEA_ERROR | 500 | Issue with the Remote Engine. Contact the Remote Engine admin or Talend Support. |
| The URI contains invalid parts | INTERNAL_INVALID_URI | The URL used to call the API contains errors, and the consumer query must be fixed. | |
| The URI contains semantic errors | INTERNAL_SEMANTIC_ERRORS_IN_URI | The syntax is valid but does not correspond to an operation compatible with the OData specifications. The consumer query must be fixed. | |
| The URI contains syntax errors | INTERNAL_SYNTAX_ERRORS_IN_URI | The URI contains unsupported or wrong characters, and the consumer query must be fixed. | |
| The content negotiation failed | INTERNAL_CONTENT_NEGOTIATION_ERROR | Compatibility issue between the file format that is requested, and the format of the dataset. The request header must be fixed. | |
| There was an error while serializing the response | INTERNAL_SERIALIZATION_ERROR | Infrastructure and data transformation issue. Contact Talend Support. | |
| There was an error while de-serializing the request | INTERNAL_DESERIALIZATION_ERROR | Infrastructure and data transformation issue. Contact Talend Support. | |
| There was a precondition error | INTERNAL_PRECONDITION_ERROR | Issue on the Talend side, where an invalid behavior is detected and the dataset information cannot be sent to the consumer. Contact Talend Support | |
| The request was malformed | INTERNAL_MALFORMED_REQUEST | Semantic or syntax issue in the URI. The consumer query must be fixed. | |
| Uncaught Olingo exception | INTERNAL_UNCAUGHT_ERROR | Unknown error. Retry the operation later or contact Talend Support. |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!