Once the Infobip SMS Function is installed, the Infobip SMS Handler inside it must be updated with your Infobip credentials. The
INFOBIP_API_KEY constant at line 3 should be populated with your Infobip API key. Note that the function should be saved and restarted after this modification.
Infobip SMS Handler looks for several properties in the messages that it processes. Messages should have to, text and from properties, and all of them should be strings. Detailed descriptions for each property can be found at Infobip API documentation.
After making a request to Infobip, SMS Handler will publish API response in
infobip-api-response channel. Structure of messages published there corresponds to response model from the API documentation linked above. Name of the response channel can be modified by changing the
RESPONSE_CHANNEL constant in the Handler code.
Lastly, SMS Handler can work as both Before Publish or Fire or After Publish or Fire function type. If used as Before Publish it will emit string messages noting if sending was successful or failed. In both cases, full API response details will still be published on infobip-api-response channel.
Copyright (c) 2018 PubNub
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.