HTTP Response Codes

FreeClimb uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error in the HTTP request provided, and codes in the 5xx range indicate an internal FreeClimb error.

Response Headers

When a POST request is made FreeClimb generates a unique request ID that is returned in the response header. FreeClimb will reuse this request ID if there are multiple webhooks for your initial request. This request ID can be used with the Performance Query Language (PQL) to Filter Logs.

200 - OKRequest was successfully processed.
201 - CreatedResource was successfully created.
202 - AcceptedRequest was successfully queued and is being processed
204 - No ContentRequest was successfully processed; the response does not include a message body.
400 - Bad RequestRequest was unacceptable, often due to an invalid parameter value or missing a required parameter.
401 - UnauthorizedAccount credentials were invalid.
403 - ForbiddenAccount credentials not authorized.
404 - Not FoundRequested resource doesn’t exist. In most cases it means the call/queue/conference/etc doesn't exist.

Note that when working with calls within queues and conferences, it may mean the particular call doesn't exist within the conference or the queue.

Using the REST API to manipulate a completed call can also result in a 404, even though the live call did exist in the past. While a completed call can be used with a GET, it can't be used with a POST.
405 - Method Not AllowedHTTP Method in the request was invalid.
409 - ConflictRequest could not be completed due to a conflict with the current state of the resource.
500, 502, 503, 504 - Server ErrorsError on FreeClimb's end.