HTTP Response Codes
Depending on request results, the Backlot REST API returns different HTTP response codes.
Note: For more information about Backlot REST API commands, see the Backlot API Reference.
|Response Code||Short Description||Comments|
|200||OK||The Backlot API successfully processed the request.|
|204||No content||The server has fulfilled the request, but does not need to return an entity-body. The response does not have a message body.|
|400||Bad request||The request is poorly formed or contains invalid data. For example, the Backlot API returns 400 response code if your request contains malformed JSON or invalid settings, such as a time setting of "25:00:00".|
|401||Not authorized||The request is not properly signed or signed with an invalid API key.|
|403||Forbidden||The request is not properly authenticated for the requested operation.|
|404||Not found||The resource does not exist. For example, if you tried to delete a video using the wrong content ID.|
|429||Insufficient "API credits" to fulfill request. See API Rate Limiting.|