Response Codes

A comprehensive breakdown of all Railz client and server-side errors.

HTTP Status CodeResponse TypeDescription
200OKEverything worked as expected.
202Data Extraction PendingThe data extraction process is ongoing in the background. At this point your flow must change to async using the webhook events.
204No Data ExtractedThe 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.
400Bad RequestThe request was unacceptable, often due to missing a required parameter.
401UnauthorizedNo valid API keys or access token provided.
403ForbiddenThe API key doesn't have permissions to perform the request or not supported on current billing plan.
404Resource Not FoundThe requested resource doesn't exist.
404Resource Not FoundThe requested resource is only available for beta users.
404Endpoint Not AllowedYou tried to access an unsupported endpoint for ASP.
409ConflictThe request conflicts with another request.
429Too Many RequestsToo many requests hit the API too quickly. We recommend an exponential backoff of your requests.
500Server ErrorAn unexpected error and could not process your request.
502Bad GatewayInvalid response received from server.
503Service UnavailableRailz is temporarily offline for maintenance. Please try again later.
504Server TimeoutThe request timed out from the server.