Nest API
Three reads: the workspace, its people and notifications. No writes at all.
Base: https://nest.eel.software/api/public/v1
Nest is the smallest surface in the suite. Three reads and not a single write.
| Method | Path | Scope | What it returns |
|---|---|---|---|
GET |
/workspace |
nest:workspace:read |
id, name, created_at |
GET |
/workspace/members |
nest:workspace:read |
The full roster |
GET |
/notifications |
nest:notifications:read |
The suite's inbox, newest first |
/workspace is the fastest way to check that a credential works. See Your
first request.
Roster and notifications
The roster arrives whole. /workspace/members returns everybody in one
response: no cursor, no limit, no search. Filter for one person by email,
or isolate a single member, on the client side over that list.
The notification feed reads from outside and marks from inside.
/notifications exposes the suite's inbox, newest first. Filter it with
recipient_id, source_app or unread_only. A user token shows that
person's own notifications by default: add recipient_id to see someone
else's, or all=true to see the whole workspace. A workspace key already
sees everyone, no parameter needed. Mark-one-read, mark-all-read and the
unread count live inside the apps: an external dashboard can show the
feed, not clear it.
Writes and MCP tools
Inviting people, changing roles, granting app access and creating workspaces
go through Nest, the app, with a person behind every action: the public API
only reads, with no POST and no PATCH.
The list of your workspaces and reference resolution across apps live as
MCP tools rather than HTTP routes:
nest_list_workspaces returns your workspaces, and suite_resolve_refs
alongside suite_search resolve and search references (EERs) across apps.