HTTP/HTTPS SMS Interface
Ready to test the HTTPS SMS interface in just a few minutes in 3 steps: Copy code ► Register ► Activate & configure API ► Test
Copy the code in the appropriate
programming language
c#
var url = "https://url.ecall.ch/api/sms";
var client = new WebClient();
var method = "POST";
var parameters = new NameValueCollection();
parameters.Add("username", "foo");
parameters.Add("password", "bar");
parameters.Add("message", "Hello eCall World");
parameters.Add("address", "0041XXXXXXXXX");
client.UploadValues(url, method, parameters);
Register & log in
An account is required to test the interface. This is free of charge.
For security reasons, you will receive your password via SMS.
Activate & configure
After registering, you can activate the API yourself in the “Interfaces” section of your account and make further configurations.
Do you need more than 40 SMS messages for testing? No problem. Contact an eCall expert
Download description
Click the link to download the description as a PDF:
Brief description of the HTTPS SMS interface
eCall’s HTTPS access allows you to directly call a URL to send messages to various call systems.
Requirements for using HTTPS access
To send messages via the HTTPS SMS interface, the following requirements must be met:
- You must have a business account with eCall (Business Package); a standard account (Private Package) is sufficient for testing (30 days)
- You must activate the HTTP interface in your eCall account
- Your software must be able to call a URL to send messages
Example
Message formats HTTPS access
Messages can be sent using GET or POST. The following rules must be observed:
- All parameters consist of a command word (ID) and the corresponding desired value
- Elements of the message are separated from each other by the “&” character (mandatory for GET; also required for POST if the Content-Type is “application/x-www-form-urlencoded”)
- The ID and value are separated by an equals sign “=”
- The IDs are case-insensitive (i.e., uppercase and lowercase letters do not matter). All characters must be transmitted in UTF-8 encoding. Additionally, characters may need to be URL-encoded (e.g., ” ” for a space, or “+” for a “+” sign)
Note:
For performance reasons, the HTTPS interface temporarily stores account settings in a cache. Therefore, changes to the settings may be reflected in the HTTP interface only after a certain delay.
