Authentication
The Splashify Pro Email API uses Bearer-token authentication. Every
request must carry a valid API key in the Authorization header.
Generating an API key
- Log in to email.splashifypro.com
- Navigate to Settings → API key
- Click Generate API key
- Copy the key. It is shown once. Lose it and you'll need to regenerate.

API keys carry the prefix pk_live_ and are 72 characters long.
An account has one active key.
Using your key
Set the Authorization header on every request:
http
Authorization: Bearer pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThe word Bearer can be in any case: bearer and BEARER work too.
cURL:
bash
curl https://api.splashifypro.com/api/v1/partner/email/quotas \
-H "Authorization: Bearer pk_live_..."Node:
javascript
fetch("https://api.splashifypro.com/api/v1/partner/email/quotas", {
headers: { Authorization: `Bearer ${process.env.SPLASHIFY_API_KEY}` },
});Python:
python
import requests, os
r = requests.get(
"https://api.splashifypro.com/api/v1/partner/email/quotas",
headers={"Authorization": f"Bearer {os.environ['SPLASHIFY_API_KEY']}"},
)Daily limits
The limit is per account, not per key, and counts the REST API, the SMTP relay and broadcasts together. Defaults:
- Sandbox: 200 sends/day
- Production: 50,000 sends/day (configurable per account)
The day is the UTC day. On a production account, past the limit:
- REST: the call stops with
429 Too Many Requestsand the messageDaily limit of N emails reached. It resets at midnight UTC.Nothing more is charged, and recipients accepted before it stay accepted. Retrying before midnight UTC gets the same answer. - SMTP: the message is refused, see SMTP Relay.
- Broadcasts: the broadcast pauses before the next email is charged. Resume it the next day and it goes on from where it stopped.
A test send of a broadcast does not count.
Key security best practices
- Never embed in client-side code. API keys go on your server, never in browser JS, mobile apps, or public repos.
- Use environment variables. Most CI / hosting platforms support
secret env vars.
.envfiles should be.gitignore'd. - Rotate periodically. Regenerate your key every 90 days at minimum, and update every service that uses it at the same time.
Replacing a compromised key
- Go to Settings → API key
- Click Regenerate API key
- Click Confirm regenerate, then copy the new key

The old key stops working at once. New requests with it get
401 Unauthorized.