eCall Business Messaging Developer Platform
eCall Business Messaging API documentation for SMS, WhatsApp, Rest API, SMPP, SOAP WebService, and HTTPS Interface integrations
Build your eCall Business Messaging integration from one hub. Use Rest API, SMPP, SOAP WebService, or HTTPS Interface based on the stack you already run.
Reach more customers on the channels they already use worldwide. Connect SMS, WhatsApp, alerts, and business messaging workflows with infrastructure built for reliable delivery.
Developers do not need another forced rewrite. They need a messaging platform that fits real systems, ships fast, and stays clear under pressure.
Rest API
Build modern SMS and business messaging integrations with HTTP endpoints, authentication, and request examples.
SMPP
Connect through SMPP when your messaging stack depends on protocol-level control and established delivery pipelines.
SOAP WebService
Use SOAP WebService when your enterprise systems rely on SOAP operations and structured service contracts.
Choose the path that fits your stack
Pick one interface and follow that documentation end to end. Each path gives developers a clear route from authentication to the first working request.
Why teams start here:
Build new messaging flows without extra protocol baggage.
Keep legacy systems moving without a full rebuild.
Move from sandbox to production with less guesswork.
Not sure where to start?
Use these rules of thumb:
Start with Rest API for modern HTTP-based integrations.
Use SOAP WebService if your system already depends on SOAP.
Use SMPP or HTTPS Interface when your delivery flow is built around those protocols.
Before you send the first request
Confirm these basics in the interface docs first:
Required credentials
Base URL or endpoint format
Required headers, fields, or payload structure
Expected success response or delivery status
Open the docs page that matches your integration, then use its sample requests, field definitions, and authentication rules as your source of truth. That keeps your first test predictable and your production rollout calmer.
Why developers choose eCall
eCall helps teams reach customers, stakeholders, and employees on trusted channels.
The platform is built for business messaging where delivery matters. That includes notifications, reminders, authentication, alerts, and operational communication.
Built for trust
Swiss-made platform with redundant data centers in Switzerland.
ISO/IEC 27001 certified for information security.
GDPR and Swiss DSG aligned for data protection.
More than 99.9% system availability.
Pick an interface
Choose the API or protocol documentation that matches your stack and transport.
Core docs
Use these API documentation pages as entry points for implementation, testing, and troubleshooting.
These pages cover Rest API endpoints, SMPP integration, SOAP WebService operations, and HTTPS Interface request flows for eCall Business Messaging.
Common messaging use cases
Build around the flows teams already run every day.
Customer communication — reminders, confirmations, reservations, delivery status
Security workflows — mTAN, OTP by SMS, two-factor authentication
Internal operations — alerts, monitoring, employee communication, scheduling
Mobile marketing — WhatsApp newsletters, SMS campaigns, info and subscription services
Why this matters
Messaging infrastructure only feels invisible when it works.
When alerts must land now, when an OTP blocks login, or when a customer waits for a status update, developers need delivery they can trust and interfaces they can ship with. That is the story of this platform.
eCall brings nearly 30 years of Swiss market experience, direct support, and multiple integration options into one product. You keep the stack that works, then connect the channel your business needs next.
Need help?
Ask a question above to get help with:
Choosing the right integration path
Understanding auth and request formats
Debugging setup and test requests
When the pressure is on, start with one interface, get one request working, and build from there.