> For the complete documentation index, see [llms.txt](https://developer.ecall-messaging.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ecall-messaging.com/readme.md).

# eCall Business Messaging Developer Platform

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question...</button>

<button type="button" class="button secondary" data-action="ask" data-query="How do I use the Rest API?" data-icon="terminal">Rest API</button><button type="button" class="button secondary" data-action="ask" data-query="How do I connect with SMPP?" data-icon="message">SMPP</button><button type="button" class="button secondary" data-action="ask" data-query="How do I integrate with the SOAP WebService?" data-icon="code">SOAP WebService</button><button type="button" class="button secondary" data-action="ask" data-query="How do I use the HTTPS Interface?" data-icon="globe">HTTPS Interface</button>

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.

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Rest API</td><td>Build modern SMS and business messaging integrations with HTTP endpoints, authentication, and request examples.</td><td><a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/0jev36QRqmTTEyLsxqEE">/spaces/XV2qPMxdz5aLVmrYopAH/pages/0jev36QRqmTTEyLsxqEE</a></td><td><a href="/files/ebMoLMpZFyLqpzByuzrk">/files/ebMoLMpZFyLqpzByuzrk</a></td></tr><tr><td>SMPP</td><td>Connect through SMPP when your messaging stack depends on protocol-level control and established delivery pipelines.</td><td><a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/dfcd591e7e7c7cc4c0ea0d5e762e5c4f7fc99167">/spaces/XV2qPMxdz5aLVmrYopAH/pages/dfcd591e7e7c7cc4c0ea0d5e762e5c4f7fc99167</a></td><td><a href="/files/ebMoLMpZFyLqpzByuzrk">/files/ebMoLMpZFyLqpzByuzrk</a></td></tr><tr><td>SOAP WebService</td><td>Use SOAP WebService when your enterprise systems rely on SOAP operations and structured service contracts.</td><td><a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/614f33ef6cf5fd97320ca610605685e3c6c65089">/spaces/XV2qPMxdz5aLVmrYopAH/pages/614f33ef6cf5fd97320ca610605685e3c6c65089</a></td><td><a href="/files/ebMoLMpZFyLqpzByuzrk">/files/ebMoLMpZFyLqpzByuzrk</a></td></tr><tr><td>HTTPS Interface</td><td>Use HTTPS Interface for direct request-based messaging integrations with simple transport and fast implementation.</td><td><a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/9b4caef8f939063fe01d210ed1de6c4c1bea7732">/spaces/XV2qPMxdz5aLVmrYopAH/pages/9b4caef8f939063fe01d210ed1de6c4c1bea7732</a></td><td><a href="/files/ebMoLMpZFyLqpzByuzrk">/files/ebMoLMpZFyLqpzByuzrk</a></td></tr></tbody></table>

{% columns %}
{% column width="50%" %}

## 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.

{% hint style="info" icon="sparkle" %}
**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.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Which interface should I use?</button>
{% endhint %}

{% hint style="warning" icon="life-ring" %}
**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

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Help me pick a starting point</button>
{% endhint %}

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.

<a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/0jev36QRqmTTEyLsxqEE" class="button primary" data-icon="terminal">Open Rest API</a> <a href="/spaces/XV2qPMxdz5aLVmrYopAH/pages/9b4caef8f939063fe01d210ed1de6c4c1bea7732" class="button secondary" data-icon="globe">Open HTTPS Interface</a>
{% endcolumn %}

{% column width="50%" %}

### 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.

{% hint style="success" icon="shield" %}
**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.
  {% endhint %}

{% stepper %}
{% step %}

#### Pick an interface

Choose the API or protocol documentation that matches your stack and transport.

* [Rest API](/api-references/rest-api.md)
* [SMPP](/api-references/smpp.md)
* [SOAP WebService](/api-references/soap-webservice.md)
* [HTTPS Interface](/api-references/https-interface.md)
  {% endstep %}

{% step %}

#### Review the setup requirements

Check authentication, endpoints, request structure, and required fields on the page you chose. Do not mix examples from different interfaces.
{% endstep %}

{% step %}

#### Send a first test request

Use the sample request from that interface page. Then confirm the response or status matches the expected result in the docs.
{% endstep %}
{% endstepper %}
{% endcolumn %}
{% endcolumns %}

### 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.

* [Rest API](/api-references/rest-api.md)
* [SMPP](/api-references/smpp.md)
* [SOAP WebService](/api-references/soap-webservice.md)
* [HTTPS Interface](/api-references/https-interface.md)

### 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.ecall-messaging.com/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.