Error Codes
When interacting with our Content API it is possible that you may encounter error codes in response to your requests if the operation was unsuccessful. The list below may change in future and so your integration should be built to handle additional error codes as and when they are introduced.
Should you encounter any error responses whilst using Stuba’s content API, they will follow the same schema.
Error Response Schema
| Field | Type | Description |
|---|---|---|
|
Success |
Boolean |
Always false for failed requests. |
|
Message |
String |
Description of the error. |
|
ErrorCode |
String |
Technical error code (e.g., SERVER_500). |
System Errors
| Error Code | Error Description |
|---|---|
|
SERVER_500 |
The system displays both errors: ‘Agency or user does not have access’ and ‘System error occurred.’ |
|
SERVER_401 |
Invalid credentials |
|
SERVER_404 |
Endpoint not found |
|
SERVER_400 |
Please provide valid credentials |
|
COUNTRY_404 |
No countries found |
|
Region_404 |
No Region found for given country |
|
Country_404 |
Please provide valid country |
|
Hotels_Country_404 |
No hotels found for the given country |
|
Hotels_City_404 |
No hotels found for the given City |
|
City_404 |
Please provide valid City |
|
HotelIds_404 |
Too many hotel ids to process. Can process only 100 hotels at a time. |
|
Hotels_404 |
No Hotel details found |
|
AUTH_400 |
Please provide valid credentials |
|
AUTH_401 |
Invalid credentials |
Response Samples
Samples
