Create a key
- Open API & MCP and stay on the API tab.
- Optionally add a label (for example, “Production agent”).
- Choose a permission preset (Read-only, Contributor, Full agent) or select individual permissions.
- Click Create API key.
- Copy the token immediately — it is shown once. Also note the Key ID.
pe_api_…. Every request needs both the token and the key id.
Permissions
Keys are scoped. Common areas include requests, comments, votes, members, users (teammates), boards, statuses, and internal notes. Grant the minimum set your integration or agent needs.Active keys
The Active keys list shows labels, permission counts, and last used time. Use Revoke to disable a key you no longer trust or need. Revocation takes effect immediately; create a new key if you must rotate.Where keys are used
- REST API —
Authorization: Bearer pe_api_…plusX-PE-API-Key-Id - MCP — same key id and token in your MCP client env (see the MCP article)
Safety checklist
- Store tokens in a secret manager or server env — never in public repos or frontend bundles.
- Prefer separate keys per environment (dev / staging / prod) and per agent.
- Revoke keys when teammates leave or a secret may have leaked.
https://api.projectecho.io/v1.
Help: [email protected] · Help Center.