Driftware

Documentation

Driftware exposes one primary channel. A client opens a long-lived request to the event endpoint and receives a keep-alive stream of state changes until it disconnects.

Endpoints

MethodPathPurpose
GET/api/v1/eventsServer-sent event stream (health, latency, deploys). Requires a project key — a request without one returns 400.
GET/api/v1/healthLiveness probe, no key needed, returns 200 ok

Pass your key as ?key= on the stream URL. Keys are issued per project from the dashboard.

Guides

Quickstart →

The stream is intentionally transport-light: a single connection replaces polling, so a client on a constrained network reconnects once and resumes where it left off.