Errors
HTTP errorsCopied!
Our API uses standardized HTTP error codes for clear and predictable responses:
- 
      
200 -
OK- Everything worked as expected. - 
      
400 -
Bad Request: The request format or content is incorrect or incomplete. This error type may also cover other unspecified 4XX status codes. - 
      
401 -
Unauthorized: No valid API key provided.- 
          
-
Invalid ApiKey For Given Resource: The required API group wasn’t enabled for the app’s API key. 
 - 
          
 - 
      
405 -
Method Not Allowed: This endpoint does accept the method you requested. - 
      
429 -
Too Many Requests: Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. - 
      
500 -
Internal Server Error: Something went wrong on Bumpups’s end. (These are rare.) - 
      
504 -
Gateway Timeout: This means your client (e.g. Postman / Zapier) timed out before our server responded. The request likely succeeded but took longer than the client’s limit. (Try the same video again— it usually completes within the timeout on a second attempt.) 
No credits are deducted when an error occurs.
Error shapes Copied!
Errors are always returned as JSON, with a top-level error object.
{
    "error": {
        "message": "error message"
    }
}
  If you receive an insufficient balance error, learn how to add credits to your developer account here.