| Response code | Meaning | Description |
|---|---|---|
| 200 | Success | Your request has been processed. You see what has been processed in the response. |
| 202 | Accepted | The request was accepted but not necessary successful. Response for booking updates. |
| 400 | Bad Request | This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again. |
| 401 | Unauthorized | A valid api_key was not provided with the request, so the API could not associate a user with the request. This could mean no api_key was provided, or the provided api_key was incorrect (or disabled). |
| 403 | ||
| 404 | Not found | Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist. |
| 406 | Not acceptable | In your configuration this endpoint does not accept data. This happens when you push data to rates and availabilities but use LOS. |
| 413 | Payload to large | The rates endpoints only accepts rateplans of a size up to 500 rateplans. If you try to push more than that, you will face this error. |
| 418 | ||
| 429 | To many requests | You push to many updates for a single apartment, most of the times at the same time for multiple endpoints. |
| 500 | Internal server error | This error lets you know our servers have experienced a problem. Please stop pushing and retry after a few seconds. If this error persists, please contact us. |
Update Restrictions
There can be only one update at a time on an apartment. When there are multiple updates on an apartment, the first request will be successful while the second one will wait for a second and throw 429 error code. This might happen since there are many APIs to update apartment details (LOS, Photos, etc.)
Best practice is to wait for requests to finish before sending the next one. If you are sending multiple requests at once, those requests should be for different apartments.
There is a 15 seconds lock in period if the update hangs or get interrupted. In such cases after the lock in period of 15 seconds, the updates can be retried again.