Skip to main content
Scopes define what actions an API key can perform. Each scope grants access to specific endpoints and operations.
Scope names follow the pattern resource:action. The wildcard * grants all current and future permissions.

Available Scopes

Campaigns

Contacts

The contact directory is your team-wide set of people, independent of any campaign. See Contacts Overview.
contacts:send_email is deliberately separate from contacts:update. A key trusted to retag the directory is not thereby trusted to spend credits and put mail on the wire from it. Grant it only to integrations that should be able to send.

Leads

A lead is one person’s membership of one campaign; a contact is the person themselves.

Sender Accounts

Domains

Replies

Webhooks

Wildcard

Only use * for administrative tools. Protect these keys accordingly — it grants contacts:send_email, so a wildcard key can spend credits.
The dashboard offers these presets when minting a key:
read_only deliberately grants no send capability of any kind — neither contacts:send_email nor replies:create.

Scope Checking

When an API request is made, ColdSend verifies the API key has the required scope:

Success Example

Insufficient Scope Example

Status: 403 Forbidden

Best Practices

  1. Principle of least privilege — Grant only the minimum scopes needed
  2. Separate keys by function — Different integrations should use different keys
  3. Audit regularly — Review which scopes your keys actually use
  4. Use compound scopes — campaigns:all is cleaner than listing each scope individually

Next Steps

Authentication

Learn how to authenticate requests using API keys.

API Keys

Create and manage API keys for your integrations.

Direct Email

The one endpoint that spends credits, and the scope that guards it.

Webhooks

Subscribe to events instead of polling.