Worker Heartbeat
API Reference
Worker Heartbeat
Receive heartbeat from a worker.
OPTIMIZATION: Uses Redis for scalable heartbeat storage instead of database. Database writes are expensive and heartbeats happen every 30s per worker.
Workers should call this endpoint periodically (e.g., every 30 seconds) to:
- Confirm they’re still alive
- Update their status (active, idle, busy)
- Report tasks processed
- Update metadata
POST
Worker Heartbeat
Authorizations
Enter your Kubiya API token (format: Bearer )
Body
application/json
Response
Successful Response