Event Pipeline

Ingest events into Cloudflare Pipelines for streaming to R2/Iceberg. When the Pipelines binding is unavailable, events append as JSON Lines to an R2 bucket.

FeaturesCopy Anchor Link

• POST /events - one event, an array (max 100), or { "events": [...] }
• GET /events/sample - example schema and accepted body shapes
• PIPELINE binding for Cloudflare Pipelines; EVENTS R2 bucket for fallback

API ReferenceCopy Anchor Link

POST /eventsCopy Anchor Link

Accepts any of:

• A single event object
• An array of event objects (max 100)
• { "events": [ ... ] }

Example RequestCopy Anchor Link

curl -X POST "https://your-worker.workers.dev/events" \
  -H "Content-Type: application/json" \
  -d '{"events":[{"type":"page_view","timestamp":"2026-01-15T12:00:00.000Z","userId":"user_123","properties":{"path":"/home"}}]}'

Success ResponseCopy Anchor Link

{
  "ok": true,
  "count": 1,
  "transport": "pipeline"
}

transport is "pipeline" when PIPELINE is bound, otherwise "r2" (appends to events/YYYY-MM-DD.jsonl).

GET /events/sampleCopy Anchor Link

Returns an example event schema and accepted request shapes.

Example RequestCopy Anchor Link

curl "https://your-worker.workers.dev/events/sample"

Error CodesCopy Anchor Link

• 400 - Invalid JSON, non-object events, or empty batch (INVALID_BODY)
• 400 - More than 100 events (TOO_MANY_EVENTS)
• 502 - Pipeline or R2 write failed (PIPELINE_ERROR)

Use CasesCopy Anchor Link

• Learn Cloudflare Pipelines ingestion from Workers
• Stream analytics or product events toward R2/Iceberg
• Fall back to R2 JSONL when Pipelines is unavailable locally
• Prototype high-volume event APIs before adding auth

LimitationsCopy Anchor Link

• Max 100 events per request
• Requires a dashboard Pipeline and/or R2 bucket matching wrangler names
• No schema validation beyond “JSON object(s)”
• R2 fallback is append-only JSONL, not a query API

DeploymentCopy Anchor Link

curl -X POST "https://your-worker.workers.dev/events" \
  -H "Content-Type: application/json" \
  -d '{"type":"page_view","timestamp":"2026-01-15T12:00:00.000Z"}'

Local DevelopmentCopy Anchor Link

cd apps/experiments/event-pipeline
npm install
npm run dev

curl -X POST "http://localhost:8787/events" \
  -H "Content-Type: application/json" \
  -d '{"type":"page_view","timestamp":"2026-01-15T12:00:00.000Z"}'

Without a Pipelines binding, wrangler dev uses the R2 fallback when EVENTS is available.

ConfigurationCopy Anchor Link

wrangler.json declares:

• Pipelines binding PIPELINE → events-pipeline
• R2 bucket EVENTS → event-pipeline-events

Cloudflare Features UsedCopy Anchor Link

• Workers - Edge compute runtime
• Pipelines - Stream events to R2/Iceberg
• R2 - JSONL fallback storage