By Sempico Solutions

HTTP API vs REST API: which is better for campaign?

The GATUM platform offers its users two types of API:

  • HTTP API – for fast integration;
  • REST API – for professional integration.

To understand what kind of integration you need to use, you need to discard your programming knowledge and just choose which one is more convenient for you.

If, for example, you need to send single SMS with some kind of information (verification codes or links), then you just need to integrate with the HTTP API. To do this, in the user’s account, simply generate a token and you are ready to send SMS via the API. This token will be with you until you delete it yourself. And even if you change the password in the User’s Cabinet, the token will remain the same. For everything to work, you need to add the correct URL structure to your software product or platform, as in the example in the account (of course, with the required number, sender’s name and text). Everything about everything can take 15 minutes, of which 10 minutes will be spent on brewing coffee.

If you decide to use the REST API, then, firstly, you need to master the OAuth2 authorization algorithm. For in order to receive a token for the REST API, it is necessary, using the login and password to enter the account, to generate this token, passing the necessary steps, according to the OAuth2 requirements. That is, if you change your password, do not forget to inform the script that sends SMS from your platform about this maneuver. By the way, this token can be used not only for one SMS / request, but also for all subsequent ones, until the token self-destructs according to its lifetime. When you were able to get hold of the token, then all roads are open to you, there is an API for you – for sending SMS (single and bulk). And as a bonus, you have the opportunity to emulate the work of a person in the user’s account. You will now be able to:
– create a database of customer numbers;
– fill it with a list of numbers;
– create a mailing list for this base;
– check information about sent SMS;
– etc.

If you have a sufficient amount of resources, you can create similar forms in your platform as we have in the User Cabinet – and enable your customers to send mailings using your platform or software.

Both versions of the API work over an encrypted protocol – HTTPS, therefore, the data transfer protocol itself from you to us takes care of the secrecy of data.

Based on the above, our recommendations for choosing an API are as follows:

By choosing the HTTP API you get:

  • fast integration;
  • a token that does not depend on password changes;
    the ability to send single SMS.
  • the ability to send single SMS.

By choosing REST API you get:

  • advanced functionality for working with our platform;
  • the authorization process becomes a little more complicated (and there is a dependence on the password to the cabinet);
  • the ability to send both single and bulk SMS;

Delivery reports (if, of course, you need them), we will send to your webhook ourselves, you just need to implement your webhook to catch reports.

IMPORTANT: Using our platform, you need to understand that each request must go after receiving a response from the previous one, because our platform can block you, as it may consider that an unauthorized attack is taking place, and in the event of an attack, we are merciless.

Therefore, if your platform or software does NOT support sending at the SMPP protocol level, then you can choose a simpler sending method – and this is API.

Having implemented the integration once – you free up your time for more interesting tasks!

If you have any questions, please contact us

Share the Post: