Response Codes
A comprehensive breakdown of all LiveAPI client and server-side errors.
HTTP Status Code | Response Type | Description |
---|---|---|
200 | OK | Everything worked as expected. |
201 | Created | Successfully created a resource. |
202 | Data Extraction Pending | The data extraction process is ongoing in the background. At this point your flow must change to async using the webhook events. |
204 | No Data Extracted | The account does not have any data for the reporting period requested. Note: Filters that result in empty data on extracted periods returns an empty array with 200 response code. |
400 | Bad Request | The request was unacceptable, often due to missing a required parameter. |
401 | Unauthorized | No valid API keys or access token provided. |
403 | Forbidden | The API key doesn't have permissions to perform the request or not supported on current billing plan. |
404 | Resource Not Found | The requested resource doesn't exist. |
409 | Conflict | The request conflicts with another request. |
500 | Server Error | An unexpected error and could not process your request. |
502 | Bad Gateway. | Invalid response received from server. |
503 | Service Unavailable | LiveAPI is temporarily offline for maintenance. Please try again later. |
504 | Server Timeout | The request timed out from the server. |
Updated 12 months ago