SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

SMPP API FAQ and Best Practices

SMPP is an industry-standard protocol designed to provide an interface for the transfer of SMS messages over the Internet. The Twilio SMPP API gives you the ability to send SMS messages between SMPP based messaging applications and Twilio to reach your customers around the world. This article answers common questions about using the Twilio SMPP API and how it’s different from other messaging solutions. 

SMPP is an industry-standard protocol designed to provide an interface for the transfer of SMS messages over the Internet. The Twilio SMPP API gives you the ability to send SMS messages between SMPP-based messaging applications and Twilio to reach your customers around the world. This article addresses common questions about using the Twilio SMPP API and how it differs from other messaging solutions.

Who is the SMPP API for?

The SMPP API is ideal for large Twilio customers who have existing SMPP deployments or are looking to use software platforms that require an SMPP interface. 

How does Twilio’s SMPP implementation differ from other SMPP products? 

Twilio's SMPP API is integrated directly into Twilio’s platform and services, allowing customers to leverage Twilio features and account management with SMPP. An active Twilio account and Twilio-managed inventory setup are required. Additional setup time may be necessary to register and configure your inventory according to regional requirements.

What messaging features does SMPP support?

With Twilio’s SMPP API you can send outbound messages and receive final delivery receipts across all Twilio-supported sender types, including short code, long code, toll-free, 10DLC, and Alphanumeric Sender IDs. This capability is available across all Twilio-supported markets. Twilio's SMPP integration also supports receiving inbound messages (MO) for supported short code and long code inventory in supported markets.

What Twilio features does SMPP support?

At launch, the SMPP API will support many Twilio messaging features including:

  • Account level functionality (market throughput, ABR, etc.)
  • Opt-Out (at the inventory level)
  • Message Filtering
  • Message Logs and Insights

What Twilio features does SMPP not support?

While the SMPP API can leverage some of Twilio’s messaging features, certain aspects of SMPP are fundamentally different and not supported. This includes Messaging Services and Messaging Service-specific features such as Link Shortening, Message Scheduling, Advanced Opt-Out, etc. Additionally, the SMPP API does not support status callbacks.

What’s the cost of the SMPP API?

The SMPP API uses standard SMS pricing, which can vary depending on your throughput and regional needs. For more information on pricing, please contact your Account Manager.

What type of messages and encoding does SMPP support?

The SMPP API currently supports messages encoded in GSM7, UCS2, Latin1, and Latin9/ASCII character encodings. Multisegment messaging is supported using the User Data Header (UDH) method. For more information on encoding, including  Data Coding and character limits, see SMPP API Messaging Encoding.

How do I get started with SMPP?

To get started with SMPP, customers should contact their account manager. Currently, there is no self-service onboarding available for the SMPP API.

How can I check the status of my SMPP messages?

SMPP traffic supports Delivery Receipts, which can be used to track the delivery of your messages. This traffic is logged in Twilio and can be accessed via the Programmable Messaging API, the Messaging section in the console, and through Messaging Insights.

How does SMPP traffic show up in my Twilio logs?

SMPP traffic is logged the same way as standard Twilio messages and is visible via the Programmable Messaging API, the Messaging logs page in the console, and through Messaging Insights. However, please note the following:

  • The Message SID in the SMPP Delivery Receipt (DLR) differs slightly from how it is logged in Twilio:
    • The SMPP DLR captures each segment, while the Twilio log captures the entire message for multisegment messages.
    • The SMPP Segment SID is a 35-character SID beginning with YV.
    • The corresponding Twilio Message SID will have the same ID, but will begin with "SM" instead of "YV".
    • For multisegment messages, the Twilio SID corresponds to the first Segment SID of the message and has no corresponding ID for additional segments. 
  • While SMPP traffic is logged in Twilio, there is currently no specific channel identifier to filter out SMPP traffic via the API or Messaging Insights, unlike other messaging channels (RCS, WhatsApp, etc.). 

Why are my SMPP messages not being sent or delivered?

Message filtering is a common reason for messages undelivered  messages and can occur to enforce Twilio’s policies or to comply with regulations and wireless carriers’ messaging policies. For more information on Twilio’s policies and how to avoid filtering, see How do I prevent my Twilio messages from being filtered blocked?

Other reasons that SMPP traffic failing to send could be related to your SMPP configuration or connection. For an overview of SMPP errors, please refer to the Error Handling section of our SMPP onboarding guide. 

Why am I not receiving SMPP messages?

SMPP supports inbound messages but requires that your sender is configured using the account-specific "Inbound routing webhook" that is provided with your SMPP credentials during initial onboarding. If you’re not receiving traffic, ensure this is configured as described in the initial setup and connection guide. 

Other reasons for not receiving traffic may include your SMPP sender not supporting inbound traffic, as in the case of Alpha Sender ID’s. 

How do SMPP messages show up on my Twilio invoice and Billing Insights?

SMPP messages are billed as standard Twilio messaging traffic and will use the same Billable Items and SKUs. Twilio may group and split messages differently depending on the network they are sent to. The encoding and number of segments of a submitted message might change during delivery, so it may not arrive exactly as originally sent. You are billed according to the number of segments actually sent, so please note that in these instances, the number of segments billed by Twilio for delivery may differ from the number of segments you sent to Twilio. 

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk