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.

FieldSize (octets)TypeDescription
Parameter Tag2Integer0x1414
Length2IntegerLength of Value field in octets
Value3C-Octet StringMKT, 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.

FieldOctets SizeTypeDescription
Parameter Tag2Integer0x1416
Length2IntegerLength of Value field in octets
Value6 to 8C-Octet Stringcreate, sign-in, transact, update, delete

max_price

If the value of this TLV is lower than the price provided by an operator for an outbound message you have submitted, the message will be rejected with an error code. Available in the submit_sm PDU. To use this tag, ask our Customer Support Team to turn on the “Enable price threshold” feature.

FieldOctets SizeTypeDescription
Parameter Tag2Integer0x1415
Length2IntegerLength of Value field in octets
ValueVariableOctet StringMax price user wants to pay for transaction

Did this page help you?