Sending a Plain SMS
| Your Application | Tall Bob |
|---|---|
| Credentials for the Tall Bob API must be included with every request, API credentials must be passed in the request header using Basic Auth. Please make sure that the API credentials point to the correct endpoint | API Credentials can be accessed via the Tall Bob Platform, instructions on how to retrieve them are outlined here |
| Sending a Plain SMS Message can be completed using this endpoint End Point: Reference Documentation URL: https://api.tallbob.com/v2/sms/send Example Request Headers: Content-Type: application/json {
| Tall Bob will take and process the request doing some basic checks to ensure that the request is well formed, expected response will be one of the below Example Responses Message Queued for Delivery {{ |
| Tracking your message delivery In order to receive updates on the processing of messages in real-time your Application will need to have a publically accessible URL Endpoint that Tall Bob can communicate with.
| Tall Bob tracks a set of events related to the lifecycle of an SMS message which can be sent back to your application. Typical events that may be received are:
{
|
Sending an MMS
| Your Application | Tall Bob |
|---|---|
| Credentials for the Tall Bob API must be included with every request, API credentials must be passed in the request header using Basic Auth. Please make sure that the API credentials point to the correct endpoint | API Credentials can be accessed via the Tall Bob Platform, instructions on how to retrieve them are outlined here |
| Sending a Plain SMS Message can be completed using this endpoint End Point: Reference Documentation URL: https://api.tallbob.com/v2/mms/send Example Request Headers: Content-Type: application/json {
| Tall Bob will take and process the request doing some basic checks to ensure that the request is well formed, expected response will be one of the below Example Responses Message Queued for Delivery {
|
| Tracking your message delivery In order to receive updates on the processing of messages in real-time your Application will need to have a publically accessible URL Endpoint that Tall Bob can communicate with.
| Tall Bob tracks a set of events related to the lifecycle of an SMS message which can be sent back to your application. Typical events that may be received are:
{
|
Contact Synchronisation between Platforms
| Your Application | Tall Bob |
|---|---|
| Credentials for the Tall Bob API must be included with every request, API credentials must be passed in the request header using Basic Auth. Please make sure that the API credentials point to the correct endpoint | API Credentials can be accessed via the Tall Bob Platform, instructions on how to retrieve them are outlined here |
Through the use of the Tall Bob API's, you have the ability to:
| Tall Bob as a part of integration is generally not considered the 'Source of Truth' when it comes to integration, as such we do not currently emit events for the editing of contact details such as the changing of a first name or the like, it is generally understood these sorts of changes will occur upstream with updates being passed to Tall Bob, one exception to this is Opt-Out status (where tall bob opt-out process is in use) |
| Tall Bob has the ability to manage opt-outs for contacts, if your application provides the ability for contacts to manage their opt out status for instance through a preference center then it is important that you implement the relevant API calls to manage the status of opt-outs with Tall Bob as outlined here | It is important that Tall Bob is kept updated with the current status of opt-out for all contacts if they are being managed externally, Opt Outs collected and managed by Tall Bob will be stored and maintained within the system, any requests from your application to send to an opted out contact will return an error message normally in the form of{With a HTTP Status 400 |
If you want to receive updates on the opt-out status of contacts you can do so by registering for the following Contact Opted Out event a typical payload, in this case, would look like this:{ |
Sending a message with an Engagement Landing Page
| Your Application | Tall Bob |
|---|---|
| Credentials for the Tall Bob API must be included with every request, API credentials must be passed in the request header using Basic Auth. Please make sure that the API credentials point to the correct endpoint | API Credentials can be accessed via the Tall Bob Platform, instructions on how to retrieve them are outlined here |
| Your application can send SMS messages which include personalised landing pages with engagement content on them, End Point: Reference Documentation URL: https://api.tallbob.com/v2/campaigns/send_via_mobile Example Request Headers: Content-Type: application/json {
| Tall Bob will take and process the request doing some basic checks to ensure that the request is well formed, expected response will be one of the below Example Response Message Queued for Delivery { |
| Tracking your message delivery In order to receive updates on the processing of messages in real-time your Application will need to have a publically accessible URL Endpoint that Tall Bob can communicate with.
| Tall Bob tracks a set of events related to the lifecycle of an SMS message which can be sent back to your application. Typical events that may be received are:
{
|
| Tracking Link Clicks and other Events If your application has the ability to store or act upon data from a third party you can register webhooks to receive this data, an example of where this might be used would be sending a discount code to people that submitted a form confirming attendance at an event  | Messages that include Engagement Campaigns can send back additional event data such as:
|
Helpful Stuff
- Looking for definitions that revolve around Mobile, SMS and Telco Industries, then click here
- More information on HTTP Status code when handling your integration can be found here
- More information on the SMS Statuses can be found here
If you ever need further assistance or someone to point you in the right direction you can email the team at [email protected]
Attachments (1)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article