Skip to Content
Browse the Docs▾

Get agent status

GET/api/v1/agent/status

Whether the agent is up and busy: sandbox state, last activity, and the next scheduled wake.

curl -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/agent/status

Response

{ "status": { "sandbox": "alive", "running": false, "lastActivityAt": 1789832474865, "lastTurnAt": 1789832490530, "pendingWakes": 2, "nextWakeAt": 1790002800000 } }

running is derived: a turn that has started, has not finished and has shown activity in the last 20 minutes. It covers the whole account, so a turn started from chat, Slack, a webhook, a workflow run or a scheduled wake counts, not just this token's messages. lastTurnAt is when the most recent of those turns finished. A dead or paused sandbox is normal between turns; the next message or wake starts one. pendingWakes counts wakes scheduled for the future, up to 100, including each workflow's next run and the daily work session, so a steady count is normal. nextWakeAt is the earliest; one well in the past means wakes are not firing.

Frequently Asked Questions

Does this show inbox warm-up or why something failed?

It shows whether Revnu is up, busy and when it next wakes. For channel numbers read GET /results. For warm-up progress or the reason something failed, ask Revnu with a message.

Which scope does this need?

results:read. A token without it gets 403 with requiredScope in the body. GET /me shows a token's scopes.

Are responses cached?

No. Every response is Cache-Control: no-store, so what you read is current.