HTTP Status Codes

The API occasionally fails to respond to requests, which is regrettable. Failures can happen for a variety of reasons. A response body in JSON format with additional information should always be returned by the API, along with an HTTP response status code that identifies the type of failure. The response body will include an error message in the event of a server issue.

200
Successfully performed the requested action

204
Successfully deleted the resource from our database

429
This error occurs for requests that exceed any of our rate limiting restrictions

400
This error usually occurs if there is a mistake in the request payload. You can check the syntax of your request to check if the parameters are appropriately named and are of correct data types.

{
    "errors": [
        {
            "errorCode": "BAD_REQUEST",
            "errorMessage": "Bad Request: Project name is missing",
            "field": "projectName"
        }
    ]
}

401
This is an error faced when you are not authenticated to access this resource. Check your api-key to see if it's not empty and contains a valid api-key that you have obtained from Rocketlane settings.

{
    "errors": [
        {
            "errorCode": "NOT_AUTHORIZED",
            "errorMessage": "Not Authorized: User not authorized"
        }
    ]
}

404
This is an error that occurs if we could not find the resource you are requesting or if we could not find the right API endpoint that you are requesting.

{
    "errors": [
        {
            "errorCode": "NOT_FOUND",
            "errorMessage": "Not Found: Resource not found for given ID"
        }
    ]
}

500
This error denotes that there is an error that occurred within our servers. The response body could help narrow down the cause for the error by our support team.

{
    "errors": [
        {
            "errorCode": "INTERNAL_SERVER_ERROR",
            "errorMessage": "Server Error: Could not perform the requested action"
        }
    ]
}