Skip to main content
Lifecycle APIs expose customer-visible machine and snapshot transitions.
Lifecycle history and webhooks require hosted or local Supabase-backed state.

List events

Per-machine events

Stream events

Use stream_events() when code needs to react to lifecycle events without polling. The iterator reconnects automatically after transport drops. On every yield it records the event ID, then reconnects with after_event_id so the API can replay missed committed events before returning to live delivery.
Supported filters include machine_id, snapshot_id, operation, status, live_only, after_event_id, replay_limit, and exact-match metadata. live_only=True skips the initial replay. After the first yielded event, the SDK still reconnects with after_event_id so reconnects do not lose events.

Webhooks

Concepts: Create, Destroy. API reference: listLifecycleEvents, listMachineLifecycleEvents, and createLifecycleWebhook.