Requests and Responses
Learn how the ClickFunnels API accepts requests and sends back responses
ClickFunnels' API expects and responds with JSON. For the optimal experience, please provide the Content-Type: application/json
header with your HTTP requests. All requests must be sent over HTTPS.
HTTP Code | Name | Description |
---|---|---|
2xx | Successful | Successful requests |
200 | OK | Successful requests, usually GET, PUT, and PATCH calls. |
201 | Created | Successful request that resulted in the creation of a record (e.g., a POST call). |
204 | No Content | Successful request that does not have an accompanying response body (e.g., a DELETE call). |
4xx | Client Error | Client-related errors that should be usually recoverable on the requesting client side. |
400 | Bad Request | The request is structured incorrectly, e.g. the body or query params are invalid or incorrectly formatted. |
401 | Unauthorized | The request could not be authenticated because of either missing or invalid Authorization Bearer token value. |
403 | Forbidden | The client tries to access a resource for which it does not possess the required permissions. |
404 | Not Found | The resource for this request is missing. |
409 | Conflict | The current app state is in conflict with the requested action. |
422 | Unprocessable Entity | The request is structurally correct but cannot be processed due to incompatible business logic or restrictions on the resource. |
429 | Too Many Requests | The API rate limits have been reached. |
5xx | Server Error | Unexpected server errors, something went wrong on our side. We will be notified and attempt to fix this as soon as possible but please don't hesitate to contact us if you see this happening. You can get in touch with us either via the discussion forum, or, if more urgent, through the ClickFunnels support. |
Updated 4 months ago