Skip to main content
Every Peel account is a team of one. Invite people and they act on your account: its APIs, saved logins, webhooks, keys and allowance. Runs and builds by any member count against the owner’s plan.

Roles

A role is a set of the same permissions keys use (Authentication). A request a role does not allow answers 403 role_permission_missing with details.role and details.required_permission.

Invite someone

Invitations are sent from the app (Settings, Team), or with a signed-in session:
Peel emails a link that works for 7 days and only for that address. The answer carries the invite_url too, so you can send it yourself. Inviting the same address again replaces the old link. A team has at most 25 people besides its owner and 50 open invitations. API keys cannot invite people. The invited person signs in with that address and opens the link, which calls POST /v1/accounts/join with the token. A link for another address answers 403 invite_email_mismatch; an expired or revoked one answers 404 invite_not_found.

Act on a team

In the app, open Team from the account menu and pick the team under Acting on; Billing is hidden while you act on a team, and Back to your account returns to your own. Keys you create in Settings while acting on a team belong to the team. Over the API with a session, send the team’s account id in a Peel-Account header; GET /v1/accounts lists the accounts you can act on. A session that is not on the team answers 403 team_access_denied. An API key always acts on the account that owns it, so a key request that sends Peel-Account answers 400 account_header_with_key. A key always acts on the account that made it. Create keys for a team with POST /v1/keys while acting on it; a key never gets more access than the person or key that made it (403 key_access_too_wide). Add api_id to limit the key to one of the team’s APIs (Keys for one API).

Manage the team

A changed role or a removal applies within 5 seconds.

Audit log

Peel records who changed what on the account: creating, changing and deleting APIs, saved logins, webhooks, keys and team members, and MCP tools that change something. Each event has the time, the person or key that did it (actor), the action as method and route, the target id and the status code. A key limited to one API that is refused is recorded where it is refused, with status 403 for a route and the JSON-RPC error code -32600 for an MCP tool call, tasks/cancel, or each refused call inside a JSON-RPC batch. Calls and runs are not in it; each run carries its own actor in Runs.
Reading it needs the team:manage permission, so owners, admins and full-access keys. Events are kept 90 days. Page with next_cursor as cursor, 1 to 100 per page.