Skip to main content

Support message_send_ttl_seconds for WhatsApp templates

Feature Request

We use POST /v1/whatsapp/templates to automatically provision Utility templates for each connected WABA.

Meta supports message_send_ttl_seconds, but Zernio’s current schema does not expose or pass this field through.

Our use case requires:

message_send_ttl_seconds: 600

so time-sensitive Utility messages expire after 10 minutes instead of using Meta’s 30-day API default.

Ideally, POST /v1/whatsapp/templates should accept and pass message_send_ttl_seconds through to Meta.

Support for updating the TTL as well, if Meta allows it, would also be useful.

Current impact: automatically provisioned templates cannot use a short TTL, which can allow stale Utility messages to be delivered long after they are relevant.

Posted by Jorge Mora S. ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Miquel Palet López

    Team•

    Sep 8

    Shipped. POST /v1/whatsapp/templates now accepts message_send_ttl_seconds and passes it to Meta, in both custom and library-template mode, so "message_send_ttl_seconds": 600 on your provisioned Utility templates works as you asked. Verified live today: the value comes back on the template read straight from Meta.

    Updating it later works too: send it on PATCH /v1/whatsapp/templates/{templateName} or the by-id variant, with or without new components (components is optional there when only the TTL changes). A TTL-only update keeps an approved template approved, no re-review. Every template read returns the field while a custom TTL is set.

    The value is checked against Meta's range for the category before the call, so you get a clear 400 with param: message_send_ttl_seconds instead of Meta's bare code 100: 30 to 900 for AUTHENTICATION, 30 to 43200 for UTILITY, 43200 to 2592000 for MARKETING. On create, -1 keeps the 30-day default for the first two.

    One thing worth knowing: if Meta recategorises a template (for example a Utility template it decides is Marketing), Meta clears the TTL. Reading the template back after a category change tells you whether that happened.

    Docs: https://docs.zernio.com/platforms/whatsapp/templates#delivery-ttl and the field on https://docs.zernio.com/whatsapp/create-whatsapp-template.

    • Jorge Mora S.

      •

      Sep 10

      Thank you very much for this. This is exactly what we needed.

      The fact that we can provision Utility templates with message_send_ttl_seconds: 600, read the value back from Meta, and update the TTL later without triggering a new review solves the issue cleanly on our side.

      I also really appreciate the extra detail about TTL being cleared if Meta recategorises the template. That is very useful for how we validate templates before sending.

      Thanks again for taking this request seriously and shipping it so quickly. It genuinely helps us keep the implementation much simpler.