The event feed: posts that became ready, and what happened to actions
GET /api/v1/events
The same events webhooks get, to read instead of receive. `signal.ready`: a post entered the ready list of the workspace's playbook, with its evidence (the quote, the link, how old it is, who answered if anyone, its rank and why it is ready) and the next actions. `action.proposed`, `action.decided` and `action.done` follow an action through the approval queue. Oldest first after the cursor `after` (an event id); pass the returned next_after to get what came since. Kept 30 days. Types: signal.ready, action.proposed, action.decided, action.done.
Any API key or OAuth token, or a signed-in member.
Parameters
| Name | Type | Description |
|---|---|---|
afterquery |
integer at least 0 |
Return events after this id (0 or omit for the oldest kept). |
typequery |
string | One of: signal.ready action.proposed action.decided action.done |
playbookquery |
string | Only events under this playbook. |
limitquery |
integer 1–200 |
Returns
{ data: [{ id, type, playbook, ref, created_at, data }], next_after, more }
Example
curl "https://sniffington.com/api/v1/events" \
-H "Authorization: Bearer $SCOUT_API_KEY"