Cloudflare Docs
Visit Logs on GitHub
Set theme to dark (⇧+D)

API configuration

​​ Endpoints

The table below summarizes the job operations available for both Logpush and Edge Log Delivery jobs. Make sure that Account-scoped datasets use /accounts/<account_identifier> and Zone-scoped use /zone/<zone_identifier>. For more information, refer to the Log fields page.

The <zone_identifier> argument is the zone id (hexadecimal string). The <account_identifier> argument is the organization id (hexadecimal string). These arguments can be found using API’s zones endpoint. The <job_identifier> argument is the numeric job id. The <dataset> argument indicates the log category (such as http_requests, spectrum_events, firewall_events, nel_reports, or dns_logs).

Operation Description API
POST Create job Zone-scoped job / Account-scoped job
GET Retrieve job Zone-scoped job / Account-scoped job
GET Retrieve all jobs for all datasets Zone-scoped jobs / Account-scoped jobs
GET Retrieve all jobs for a dataset Zone-scoped jobs / Account-scoped jobs
GET Retrieve all available fields for a dataset Zone-scoped fields / Account-scoped fields
PUT Update job Zone-scoped job / Account-scoped job
DELETE Delete job Zone-scoped job / Account-scoped job
POST Check whether destination exists Zone-scoped job / Account-scoped job
POST Get ownership challenge Zone-scoped job / Account-scoped job
POST Validate ownership challenge Zone-scoped job / Account-scoped job
POST Validate log options Zone-scoped job / Account-scoped job

For concrete examples, refer to the tutorials in Logpush examples.

​​ Connecting

The Logpush API requires credentials like any other Cloudflare API.

$ curl -s -H "X-Auth-Email: <EMAIL>" -H "X-Auth-Key: <API_KEY>" \

​​ Ownership

Before creating a new job, ownership of the destination must be proven.

To issue an ownership challenge token to your destination:

$ curl -s -X POST{zone_identifier}/logpush/ownership \
-H "X-Auth-Email: <EMAIL>" \
-H "X-Auth-Key: <API_KEY>" \
-H "Content-Type: application/json" \
--data '{"destination_conf":"s3://<BUCKET_PATH>?region=us-west-2"}' | jq .

A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path, if appropriate for your destination):

"errors": [],
"messages": [],
"result": {
"valid": true,
"message": "",
"filename": "<path-to-challenge-file>.txt"
"success": true

You will need to provide the token contained in the file when creating a job.

​​ Destination

You can specify your cloud service provider destination via the required destination_conf parameter.

  • Cloudflare R2: bucket path + account ID + R2 access key ID + R2 secret access key; for example: r2://<BUCKET_PATH>?account-id=<ACCOUNT_ID>&access-key-id=<R2_ACCESS_KEY_ID>&secret-access-key=<R2_SECRET_ACCESS_KEY>
  • AWS S3: bucket + optional directory + region + optional encryption parameter (if required by your policy); for example: s3://bucket/[dir]?region=<REGION>[&sse=AES256]
  • Datadog: Datadog endpoint URL + Datadog API key + optional parameters; for example: datadog://<DATADOG_ENDPOINT_URL>?header_DD-API-KEY=<DATADOG_API_KEY>&ddsource=cloudflare&service=<SERVICE>&host=<HOST>&ddtags=<TAGS>
  • Google Cloud Storage: bucket + optional directory; for example: gs://bucket/[dir]
  • Microsoft Azure: service-level SAS URL with https replaced by azure + optional directory added before query string; for example: azure://<BlobContainerPath>/[dir]?<QueryString>
  • New Relic New Relic endpoint URL which is for US or for EU + a license key + a format; for example: for US "<NR_LICENSE_KEY>&format=cloudflare" and for EU "<NR_LICENSE_KEY>&format=cloudflare"
  • Splunk: Splunk endpoint URL + Splunk channel ID + insecure-skip-verify flag + Splunk sourcetype + Splunk authorization token; for example: splunk://<SPLUNK_ENDPOINT_URL>?channel=<SPLUNK_CHANNEL_ID>&insecure-skip-verify=<INSECURE_SKIP_VERIFY>&sourcetype=<SOURCE_TYPE>&header_Authorization=<SPLUNK_AUTH_TOKEN>
  • Sumo Logic: HTTP source address URL with https replaced by sumo; for example: sumo://<SumoEndpoint>/receiver/v1/http/<UniqueHTTPCollectorCode>

For R2, S3, Google Cloud Storage, and Azure, logs can be separated into daily subdirectories by using the special string {DATE} in the URL path; for example: s3://mybucket/logs/{DATE}?region=us-east-1&sse=AES256 or azure://myblobcontainer/logs/{DATE}?[QueryString]. It will be substituted with the date in YYYYMMDD format, like 20180523.

For more information on the value for your cloud storage provider, consult the following conventions:

To check if a destination is already in use:

$ curl -s -XPOST{zone_identifier}/logpush/validate/destination/exists -d '{"destination_conf":"s3://foo"}' | jq .


"errors": [],
"messages": [],
"result": {
"exists": false
"success": true

​​ Job object

​​ Kind

The kind parameter (optional) is used to differentiate between Logpush and Edge Log Delivery jobs. For Logpush jobs, this parameter can be left empty or omitted. For Edge Log Delivery jobs, set "kind": "edge". Currently, Edge Log Delivery is only supported for the http_requests dataset.

curl -s -X POST '{zone_identifier}/logpush/jobs' \
-H "X-Auth-Email: <EMAIL>" \
-H "X-Auth-Key: <API_KEY>" \
-d '{
"dataset": "http_requests",
}' | jq .

​​ Options

Logpull_options has been replaced with Custom Log Formatting output_options. Please refer to the Log Output Options documentation for instructions on configuring these options and updating your existing jobs to use these options.

If you are still using logpull_options, here are the options that you can customize:

  1. Fields (optional): Refer to Log fields for the currently available fields. The list of fields is also accessible directly from the API:{zone_identifier}/logpush/datasets/{dataset}/fields. Default fields:{zone_identifier}/logpush/datasets/{dataset}/fields/default.
  2. Timestamp format (optional): The format in which timestamp fields will be returned. Value options: unixnano (default), unix, rfc3339.
  3. Redaction for CVE-2021-44228 (optional): This option will replace every occurrence of ${ with x{. To enable it, set CVE-2021-44228=true.

To check if the selected logpull_options are valid:

curl{zone_identifier}/logpush/validate/origin \
--header "X-Auth-Email: <EMAIL>" \
--header "X-Auth-Key: <API_KEY>" \
--data '{
"logpull_options": "fields=RayID,ClientIP,EdgeStartTimestamp&timestamps=rfc3339&CVE-2021-44228=true",
"dataset": "http_requests"


"errors": [],
"messages": [],
"result": {
"valid": true,
"message": "",
"success": true

​​ Filter

Use filters to select the events to include and/or remove from your logs. For more information, refer to Filters.

​​ Sampling rate

Value can range from 0.0 (exclusive) to 1.0 (inclusive). sample=0.1 means return 10% (1 in 10) of all records. The default value is 1, meaning logs will be unsampled.

​​ Max Upload Parameters

These parameters can be used to gain control of batch size in the case that a destination has specific requirements. Files will be sent based on whichever parameter is hit first. If these options are not set, the system uses our internal defaults of 30s, 100k records, or the destinations globally defined limits.

  1. max_upload_bytes (optional): The maximum uncompressed file size of a batch of logs. This setting value must be between 5MB and 1GB. Note that you cannot set a minimum file size; this means that log files may be much smaller than this batch size.
  2. max_upload_records (optional): The maximum number of log lines per batch. This setting must be between 1000 and 1,000,000 lines. Note that you cannot specify a minimum number of log lines per batch; this means that log files may contain many fewer lines than this.
  3. max_upload_interval_seconds (optional): The maximum interval in seconds for log batches. This setting must be between 30 and 300 seconds. Note that you cannot specify a minimum interval for log batches; this means that log files may be sent in shorter intervals than this.

​​ Custom fields

You can add custom fields to your HTTP request log entries in the form of HTTP request headers, HTTP response headers, and cookies. Custom fields configuration applies to all the Logpush jobs in a zone that use the HTTP requests dataset. To learn more, refer to Custom fields.

​​ Audit

The following Logpush actions are recorded in Cloudflare Audit Logs: create, update, and delete job.