death by kid
Eternal Poster
Endpoints
The API is accessed by making HTTPS requests to a specific version endpoint URL, in which GET, POST, PUT, ρá†ch, and DELETE methods dictate how your interact with the information available. Every endpoint is accessed only via the SSL-enabled HTTPS (port 443) protocol.
Everything (methods, parameters, etc.) is fixed to a version number, and every call must contain one. The latest version is Version 4.
The stable base URL for all Version 4 HTTPS endpoints is:
You do not have permission to view the full content of this post. Log in or register now.
Requests
Requests must be sent over HTTPS with any payload formatted in JSON. Depending on if a request is authenticated with the new API Tokens or the old API Keys, required headers differ and are detailed below.
API Tokens
API Tokens provide a new way to authenticate with the Cloudflare API. They allow for scoped and permissioned access to resources and use the RFC compliant You do not have permission to view the full content of this post. Log in or register now..
Required parameters
Name
Format
Description
API Token
Authorization: Bearer <token>
API Token generated from the You do not have permission to view the full content of this post. Log in or register now.
Example request
Requests are generally formatted as follows:
GET object/
bject_id
API Token cURL (example)
curl -X GET "You do not have permission to view the full content of this post. Log in or register now." \
-H "Content-Type:application/json" \
-H "Authorization: Bearer YQSn-xWAQiiEh9qM58wZNnyQS7FUdoqGIUAbrh7T"
API Keys
All requests must include both X-AUTH-KEY and X-AUTH-EMAIL headers to authenticate. Requests that use X-AUTH-USER-SERVICE-KEY can use that instead of the Auth-Key and Auth-Email headers.
The API is accessed by making HTTPS requests to a specific version endpoint URL, in which GET, POST, PUT, ρá†ch, and DELETE methods dictate how your interact with the information available. Every endpoint is accessed only via the SSL-enabled HTTPS (port 443) protocol.
Everything (methods, parameters, etc.) is fixed to a version number, and every call must contain one. The latest version is Version 4.
The stable base URL for all Version 4 HTTPS endpoints is:
You do not have permission to view the full content of this post. Log in or register now.
Requests
Requests must be sent over HTTPS with any payload formatted in JSON. Depending on if a request is authenticated with the new API Tokens or the old API Keys, required headers differ and are detailed below.
API Tokens
API Tokens provide a new way to authenticate with the Cloudflare API. They allow for scoped and permissioned access to resources and use the RFC compliant You do not have permission to view the full content of this post. Log in or register now..
Required parameters
Name
Format
Description
API Token
Authorization: Bearer <token>
API Token generated from the You do not have permission to view the full content of this post. Log in or register now.
Example request
Requests are generally formatted as follows:
GET object/
bject_idAPI Token cURL (example)
curl -X GET "You do not have permission to view the full content of this post. Log in or register now." \
-H "Content-Type:application/json" \
-H "Authorization: Bearer YQSn-xWAQiiEh9qM58wZNnyQS7FUdoqGIUAbrh7T"
API Keys
All requests must include both X-AUTH-KEY and X-AUTH-EMAIL headers to authenticate. Requests that use X-AUTH-USER-SERVICE-KEY can use that instead of the Auth-Key and Auth-Email headers.
