API keys let Claude, Cursor, Clay, n8n or your own code act on one workspace. Only admins can create or revoke them.
Create a key
- Go to Settings, API.
- Name the key after where it will be used (Claude, Clay, n8n), so you know what to revoke later.
- Choose Read and write or Read only, then click Create key.
- Copy the key (it starts with
echo_sk_) and click I saved it. It is shown once; Echo keeps only a fingerprint.
Access levels
| Read only | Read and write | |
|---|---|---|
| List and read campaigns, leads, groups, designs, signals, links | Yes | Yes |
| Import leads | No | Yes |
| Create (publish) campaigns, spending AI on your key | No | Yes |
| Send links into your sequencer | No | Yes |
Good practice
- One key per tool or person. The table shows each key's Last used date.
- Store keys in your secret manager or environment variables (
ECHO_API_KEY), never in code or shared docs. - Revoke stops a key at once. Anything using it gets
401from then on. - Limits: 120 requests a minute per key, up to 20 active keys per workspace.
Next: MCP server or REST API.