In case of connection with vendor via HTTP, the SMS switch has to understand the vendor’s responses and learn how to handle them. That becomes possible with the vendor’s HTTP parser implementation.
In order to implement a new HTTP parser properly, the following information must be provided from the vendor:
1) full API documentation and/or an example of a request for sending an SMS with the response sample from the vendor;
2) full trace of a request-reply samples;
3) if the request for sending an SMS implies authorization (basic or via bearer or any other), the respective credentials (login/password/token/api key/etc...) should be sent;
4) destination number/sender ID/text and other parameters (if applicable) which can be used to send test SMSs;
5) the way the system should handle delivery reports:
5.1) in case they support queries — the format of the request and the sample of the response to it should be supplied;
5.2) in case they support callbacks (more preferable) — the format of the callback and the sample of the response they expect to receive back should be provided to the Alaris technical support team;
6) prepare the configuration on your platform for new vendor implementation. You should create Carrier/Account/Agreement/Product and upload the rates into the product. Then, share with the Alaris technical support team the Carrier ID, so our team could proceed with channel configuration as soon as the parser is ready.
AKBSMS - Alaris Knowledge Base
Related Questions:
HTTP vendor
HTTP parser implementation
HTTP queries
callbacks
Link to this article: https://helpdesk.alarislabs.com/en/knowledge_base/article/248/category/131/