The API is REST over HTTPS. All payloads are JSON and all timestamps are RFC 3339 in UTC. Keys are passed in a request header and can be limited to a single pipeline.
A pipeline is a source, a sink and a schema that ties them together. Everything else, batching, retries and ordering, is handled for you.
| Part | Options | Notes |
|---|---|---|
| Source | Queue, webhook, database log | One source per pipeline |
| Sink | Warehouse, object storage, HTTP endpoint | Multiple sinks may share a source |
| Schema | Versioned, for example orders@v3 | A breaking change is rejected at publish time |
| Mode | Guarantee | Notes |
|---|---|---|
| at-least-once | No loss | Default. Consumers must be idempotent. |
| exactly-once | No loss, no duplicates | Requires a sink that supports transactions. |
A backfill replays a date range into one consumer without disturbing the others. Progress is shown in the console and the job can be paused at any point.
Engineering support answers within one business day. Include the pipeline name and a trace id.