Authentication
Every request to the SubscribeFlow API requires an API key.
API key format
| Prefix | Environment | Purpose |
|---|---|---|
sf_live_ |
Production | Real subscribers, real emails |
sf_test_ |
Testing | Sandbox data, no emails sent |
Create keys in the Dashboard under Settings > API Keys.
Warning
API keys are shown only once at creation. Store them securely -- you cannot retrieve them later.
Sending your API key
Include the key in every request using one of these headers:
Example authenticated request
Scopes
Each API key can be restricted to specific scopes. If no scopes are set, the key has full access.
| Scope | Description |
|---|---|
subscribers:read |
List and get subscribers |
subscribers:write |
Create and update subscribers |
subscribers:delete |
Delete subscribers |
tags:read |
List and get tags |
tags:write |
Create, update, and delete tags |
templates:read |
List and get email templates |
templates:write |
Create, update, and delete templates |
emails:send |
Send transactional emails |
campaigns:read |
List and get campaigns |
campaigns:write |
Create, update, send, and cancel campaigns |
triggers:read |
List and get email triggers |
triggers:write |
Create, update, and delete triggers |
webhooks:manage |
Create, update, delete, and test webhooks |
api-keys:manage |
Create and revoke API keys |
Tip
Follow the principle of least privilege. A key that only sends emails should have the emails:send scope and nothing else.
Rate limits
All API keys are rate-limited to 1,000 requests per minute. When you exceed this limit, the API returns HTTP 429 Too Many Requests with a Retry-After header indicating how many seconds to wait.