HTTP Errors

You may receive a variety of errors from our API. This matrix shows what you might expect, why, and whether it is safe to retry these requests.

HTTP Status	Description	May retry?
400	There is a problem with one of the inputs for the request. Expect a JSON response with an error member with a human-readable explanation of the problem.	No
401	The provided API key is not valid.	No
404	Requests will return a 404 when the referenced resource is not available	No
405	If an endpoint is called with a HTTP method that it does not support, this response code will be returned.	No
429	If the client makes too many requests to the API within a period of time, this response code will be returned. This may be returned when an integration’s limits have been reached.	Yes
502	This error is returned when Runway is shedding load	Yes
503	This error is returned when Runway is shedding load	Yes
504	This error is returned when Runway is overloaded and not able to satisfy the request	Yes

When retrying requests due to an error, implement exponential backoff and jitter. To implement jitter, add a random delay of up to 50% to your retry timing: doing this prevents thundering herds.

Note: Runway’s SDKs will handle retries automatically.