Issue a request to the URL
https://gateway.sms77.io/api and send the needed variables optionally as
HTTP GET or
HTTP POST parameters. For security reasons and also when sending larger items to many recipients or for longer SMS texts, we recommend calling via
Alternatively, you can also transfer the data directly as JSON in the post body. To do this, set the header
content-type: application/json – you should also set
accept: application/json to get JSON as response.
Please make sure that all parameters are transmitted in a URL-encoded form before you send the request.
The authentication to the HTTP Api is done by passing your your api key as
POST parameter. Please use the following values:
||your api key – you will find it in your login under Developer > API Keys|
Authentication via HTTP Basic Authentication would be more secure. To do this, send the following header to our API:
Authorization: basic YOUR_API_KEY
All our interfaces are limited to a maximum of 50 connections per second. Please bundle your requests accordingly, e.g. by sending several SMS in one request. If you still want to send more requests per second, please use keep-alive of the connection. This way you avoid the overhead of a connection setup.
To secure your account, we have implemented the following security mechanisms:
1. Api Key
Access to the API is only possible with your API key. If a third party accesses your account, they will still not be able to log in. You can find your Api Keys in your login under the Developer item in the API Keys section. You can add different keys via the green plus.
2. IP Whitelist
To increase security, you can enter one or more IPs in your login under Developer in the API Keys section, from which the HTTP Api may be accessed via your account. You can access the settings by clicking on the blue cogs.
It is also possible to specify a host name, which is then resolved and checked by the API during the call. Several values can be entered comma-separated. Please note that the whitelist only makes sense in combination with a static IP address.
3. SSL encryption
A call of the API via http:// is possible, however we recommend to use the encrypted transmission via SSL for security reasons. To do this, use the URL