MagicBell vs SuprSend

MagicBell

A public OpenAPI 3.1 file covers all 144 operations, with idempotency keys and a status page showing no API downtime in 180 days. No batching or digest step, llms.txt, error code list, SLA or sub-processor list was found, and project tokens carry no scopes.

SuprSend

MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.

MagicBell

1. Ask the owner for a Project JWT from the dashboard's Project Auth page. The terms forbid accounts registered by automated methods
2. Send Idempotency-Key with a UUID on POST /v2/broadcasts, and reuse it on a retry within 24 hours
3. Stay under 500 requests a minute per IP. A 429 blocks the address for 60 seconds, so put many recipients in one broadcast
4. Use a Project JWT for broadcasts, users, integrations and workflows, and a User JWT for one user's inbox, tokens and preferences
5. Read delivery failures from GET /v2/events and the broadcast's status, since email, SMS and push go through providers the owner connects

SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with --tools set to read-only groups for production workspaces
3. Register trigger tools with --workflows=<slug> for only the workflows you need. The default registers none
4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
5. Treat management API responses as secrets. They include the workspace secret in plain text