SMS API - SMPP TLVs
This page provides the technical details needed to develop Short Message Peer-to-Peer (SMPP) clients using the TeleSign SMS API.
If you haven’t already, first review SMPP Protocol to learn our general SMPP requirements before reading this page.
Additional TLVs Supported
These TLVs are supported only when using SMPP to hit the TeleSign SMS API.
message_type (required)
The purpose for which your outbound message is being sent. Always required when hitting the SMS API.
Expected values are:
OTP
(for a one-time password)MKT
(for a marketing message)ARN
(for an alert, reminder, or notification)
If this field is missing or has an unexpected value, the message is rejected with a 0x000000C3
(Expected TLV missing) or a 0x000000C4
(Invalid TLV Value) error code.
Field | Size (octets) | Type | Description |
---|---|---|---|
Parameter Tag | 2 | Integer | 0x1414 |
Length | 2 | Integer | Length of Value field in octets |
Value | 3 | C-Octet String | MKT , ARN , or OTP |
account_lifecycle_event
Use this to indicate what phase of the account lifecycle the end user is in when you send a transaction.
Field | Octets Size | Type | Description |
---|---|---|---|
Parameter Tag | 2 | Integer | 0x1416 |
Length | 2 | Integer | Length of Value field in octets |
Value | 6 to 8 | C-Octet String | create , sign-in , transact , update , delete |
Updated 4 months ago