Response Codes

The First Street API uses standard HTTP response codes to indicate success or failure of a particular request. Below is a list of the response codes you could see and what they mean.

Please note there is a delineation between API Successful Errors vs Server Error; e.g., A successful API error will always return HTTP 200 where as an internal server error could return HTTP 500 or HTTP 400.

HTTP Code	Description
200	Success - Successful API Request, however it does not neccessairly mean the query was a success.
401	Unauthorized - API Key is unauthorized or account is not active
403	Forbidden - A request made without a valid API key
404	Not Found - The requested resource does not exist
400	Bad Request - Specific query parameters are missing from request
422	Unprocessable Content - Double check your GraphQL query to assure that it conforms to the Working with the GraphQL API schema.
429	Too Many Requests - Too many requests have been made within a given amount of time, see Rate Limits for additional information.
500	Internal Server Error- if this persists, please email [e-mail]
501	Not Implemented - The requested service hasn't been implemented. Check URL.
502	Bad Gateway - Internal error, if this persists, please email [e-mail]
503	Service Unavailable - Internal error, if this persists, please email [e-mail]
504	Gateway Timeout - Internal error from our upstream provider. If this persists, please email [e-mail].