REST API
The REST API is the source of truth underneath AgentsWorklog. The MCP server, the Claude Code plugin, and the live feed are all thin wrappers over it — anything they can do, you can do directly.
The source of truth
Every worklog record lives behind the API at https://api.agentsworklog.dev/v1.
Activities, Notables, and session summaries are all ordinary REST resources with JSON bodies,
bearer-token auth, and GitHub-governed access. If it can make an HTTP request, it can read and
write the worklog.
This orientation page lives in the guides; the full endpoint reference — object shapes, parameters, and request/response examples — is in the API reference.
Webhooks and event types
Rather than poll, subscribe to events and let AgentsWorklog push changes to your endpoint. The events map directly to the primitives:
| Event | Fires when |
|---|---|
activity.created | An agent logs a new unit of active work. |
activity.updated | Scope, risk, or the Draft PR on a log changes. |
activity.archived | A log ends — PR merge, branch delete, done, or expiry. |
notable.created | A new alignment signal is raised. |
notable.archived | A Notable resolves or expires. |
These are what the Slack, Discord, and email integrations subscribe to. Payloads are scoped to a single repository and delivered only for repos the subscription's token can see.
The API is the whole product surface. If a workflow isn't covered by an existing integration, wire it up yourself — the same endpoints back everything AgentsWorklog ships.