SendPulse API
SendPulse REST API — omnichannel marketing automation platform supporting email, SMS, web push, Viber, WhatsApp, Facebook Messenger, and chatbots via a unified API, enabling agents to orchestrate multi-channel marketing campaigns and automation flows.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
GDPR compliant. TLS enforced. OAuth2 token-based auth is better than API key for some scenarios. EU and US data centers. No SOC2. CAN-SPAM compliant for US email marketing.
⚡ Reliability
Best When
You need a cost-effective omnichannel marketing platform (email + SMS + push + chatbots) with a single API, especially for non-US markets where pricing is competitive.
Avoid When
You need sophisticated enterprise marketing automation or developer-first transactional email — SendPulse is best as a marketer-managed platform with API for automation.
Use Cases
- • Agents triggering omnichannel marketing campaigns (email + SMS + push) via single SendPulse API for coordinated outreach
- • Chatbot automation — agents creating and managing SendPulse chatbot flows for WhatsApp and Messenger without code
- • Email list management — agents syncing subscriber lists, managing segments, and triggering email campaigns based on user actions
- • Transactional messaging — agents sending transactional emails, SMS, and push notifications for order confirmations and alerts
- • Automation workflows — agents triggering SendPulse automation sequences based on CRM events and customer lifecycle stages
Not For
- • Developer-first email — SendPulse is a marketing platform, not a transactional email API; use SendGrid or Postmark for pure transactional email
- • Enterprise marketing automation — Marketo or HubSpot have more sophisticated enterprise automation features
- • US-only teams — SendPulse is popular in Eastern Europe and Latin America; support and documentation best in those regions
Interface
Authentication
OAuth2 client credentials flow for machine-to-machine access. Client ID and Client Secret from SendPulse account. Access token expires after 1 hour and must be refreshed. No scope granularity — full account access.
Pricing
Generous free tier for small lists. Pricing competitive for Eastern European and Latin American markets. SMS pricing varies by country. Chatbot and push notifications available on all paid plans.
Agent Metadata
Known Gotchas
- ⚠ OAuth access token expires every 1 hour — agents must implement token refresh logic and handle 401 responses by re-authenticating
- ⚠ Campaign sends are not idempotent — agents must track whether a campaign was sent to avoid duplicate sends
- ⚠ SMS pricing and availability vary significantly by country — verify coverage before building SMS workflows
- ⚠ API documentation quality is uneven — some endpoints are poorly documented; test before relying on undocumented behavior
- ⚠ Domain verification required for email sending — agents must ensure sending domain is verified before triggering campaigns
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for SendPulse API.
Scores are editorial opinions as of 2026-03-06.