Cloudflare Logpush

curl -X POST http://localhost:5080/api/v1/_cloudflare \
  -H 'X-Connector-Token: <push_token>' \
  -H 'content-encoding: gzip' \
  --data-binary @logs.ndjson.gz

curl -X POST http://localhost:5080/api/v1/_cloudflare \
  -H 'X-Connector-Token: <push_token>' \
  -H 'content-encoding: gzip' \
  --data-binary @logs.ndjson.gz

POST /api/v1/_cloudflare

Accepts NDJSON, including the gzip-encoded body that Cloudflare Logpush commonly sends. The endpoint does not use a bearer token. Create a connector of kind cloudflare_logpush with a push_token of at least 16 characters and a target_stream, and send the token in the header X-Connector-Token. The query parameter ?token= also works. A wrong token answers 401. Each line becomes one log event in the target_stream (default cloudflare). The fields of the line are stored as they are, and the event time is the time of receipt. The endpoint answers 204 on success.

curl -X POST http://localhost:5080/api/v1/_cloudflare \
  -H 'X-Connector-Token: <push_token>' \
  -H 'content-encoding: gzip' \
  --data-binary @logs.ndjson.gz

See Connectors for the connector setup.

Last modified on October 26, 2026

Overview

Authentication

Intake

Query

APM

RUM

Streams

Alerting

Correlation & Web

Platform & Administration