📘
Sinch | Documentation Global
  • Introduction
  • Glossary
  • GETTING STARTED - MENU
    • Sinch Messaging Platform
      • Login, Language & Menu
      • Account & Settings
      • Dashboard
      • Contacts
      • Groups
  • Credits and limits
    • Signing of plans
    • Limits
  • Send a message
    • Send a fast message
    • How to Send a Message
    • How to Set Up a File
    • Mapped errors
    • Campaigns
    • Correlation ID
    • Tracking Sent Messages
    • Cancelling a Message
    • Character Limit Setting
    • MM2: New Report: Chat (MT + MO)
    • SMS Report > RCS
  • Reports
    • Viewing & Exporting Reports
      • New WhatsApp Conversation report
      • Getting to know the new reports
    • Saved Reports
    • WhatsApp Lists
    • Billing Report
  • Permission
    • System User Role
    • Managing Customers | Subaccounts
    • Permission Levels
    • Subaccounts & Users
    • IP Restriction
    • Two-step Verification
  • SMS
    • SMS Template
    • SMS BOT
  • RCS
    • RCS (Native)
  • WHATSAPP
    • WhatsApp Embedded Signup
      • Prerequisites
      • Registering your WhatsApp Number
      • Verifying your Company on Business Manager
      • Potential Errors During the Embedded Signup Flow
    • Human Assistance Policy
    • WhatsApp Guidelines
    • Instructions & Good Practices
      • Channel Rules
      • Learn More About Tiers
      • Good Practices
    • WA Template - What Is It?
    • Registering a Template
    • Deleting a WA Template
    • WhatsApp Account Settings
    • WhatsApp Dashboard
    • Tech Providers - What is it and how does it work?
  • IA CONVERSATIONAL
    • Planning your bot
    • Creating a new bot
    • Adding content to your bot
      • Detecting information in expressions
      • Asking user info through input validation
      • Flow navigation with variables
    • Bot dialogs
      • Bot message
      • Go To
      • Input Validation
      • Action
    • Publishing & platform URLs FAQ
  • TECHNICAL DOCUMENTATION
    • API & Integrations
      • Introduction - Integrations
      • SMS API
      • Email API
      • Fallback API
      • WhatsApp API
      • WhatsApp Groups API
      • Listing Message Templates
      • WhatsApp Interactive API
      • WhatsApp Lists via API
      • WhatsApp Messaging via SFTP
      • Campaigns API
      • TTL - Time to Live
      • Webhook
  • SUPPORT
    • Status
    • Glossary - Status Page Components
    • Support
  • STATUS PAGE
    • Components status page
      • Integrations
        • SMPP
        • Web service API
        • Web Interface
      • Callback / Delivery Report
        • Webhook DLR (delivery to handset)
        • SMPP DLR (delivery to handset)
        • SMPP Callback (delivery to carrier)
        • Webhook Callback (delivery to carrier)
      • OPERATORS
      • WhatsApp Sending messages to the user (MT)
        • Internal Queues MT
      • WhatsApp Receiving User Messages (MO)
        • Internal Queues (MO)
Powered by GitBook
On this page
  • Messaging with TTL (Time to Live - The HSM’s lifespan before being delivered)
  • From v2.21.3 (https://developers.facebook.com/docs/whatsapp/changelog#app) onwards, you can inform the TTL (in days) for the delivery of your messages to expire (i.e., their Time to Live).
  • Call for Messaging via FTP with TTL
  • Call for Messaging via API with TTL

Was this helpful?

  1. TECHNICAL DOCUMENTATION
  2. API & Integrations

TTL - Time to Live

Messaging with TTL (Time to Live - The HSM’s lifespan before being delivered)

PreviousCampaigns APINextWebhook

Last updated 3 years ago

Was this helpful?

Messaging with TTL (Time to Live - The HSM’s lifespan before being delivered)

Feature Description:

From v2.21.3 () onwards, you can inform the TTL (in days) for the delivery of your messages to expire (i.e., their Time to Live).

  • Companies can use this to ensure messages aren’t delivered on dates later than what was set.

  • Currently, TTL can only be set for HSM messages ().

  • If a message is not delivered to the customer before the period set as limit, i.e. it expires, then the message will no longer be delivered.

  • A status notification (CallBack) will be sent by WA.

  • The status notification can be sent to our customers so long as it is configured.

IMPORTANT: setting a TTL has the following limitations:

  • Only HSM messages

  • minimum 1 day (24 hours) from the time the message is sent

  • maximum 30 days

  • default 7 days. (Currently, this value can be altered)

  • the TTL is effective from the moment your message is sent, that is, if a message is scheduled, the TTL will be attributed by adding the value to the date when it was triggered.

  • If a message receives a value of less than 1 day or greater than 30 days, our platform will, at the time of delivery, attribute values within the permitted limit.

  • This behavior has been implemented to prevent us from having issues when delivering messages, as, if there is an attempt to deliver a message that does not observe the minimum and maximum TTL values, this message will be denied by the container.

Call for Messaging via FTP with TTL

Messaging example: 2019-01-18;11:0;11:15;HSM;chatclub_welcome;pt_BR;DETERMINISTIC;name|company;2 phone;name;company 5519998873499;mozart;wavy 5519981794226;diego;wavy The information that represents the TTL is at the end of the first line, after the HSM parameters.

This information will be an INTEGER that is represented in number of days. That is, we will have a 2-day TTL. This means that, after 2 days from the date and time the message is sent, if the recipient has not received the message, this message WILL NO LONGER BE DELIVERED.

Call for Messaging via API with TTL

{
 "destinations": [{
 "correlationId": "MyCorrelationId",
 "destination": "5519900001111"
 }],
 "message": {
 "ttl": 1,
 "hsm": {
 "namespace": "namespace",
 "elementName": "elementName",
 "parameters":[
 "MyParam1",
 "MyParam2"
 ]
 }
 }
 }

https://developers.facebook.com/docs/whatsapp/changelog#app
access HSM information