Skip to main content
GET
List template library

Concepts

Meta keeps a library of ready-made templates for common use cases — order confirmation, delivery notice, verification code. Templates created from it skip review: they are approved from the start. This endpoint lists what is available for your WABA.
The library is defined by Meta and varies by category and language. You cannot add templates to it.
To create a regular template, which does go through review, use API reference.

How to find out which models exist

The list belongs to Meta and changes over time, so you query it instead of memorizing it. The endpoint above returns the models available to your WABA, and each one comes with its topic and use case.
On Meta’s Graph API, the search (GET /message_template_library) accepts the topic, usecase, industry and language filters, plus search and name. Our route does not pass those filters through today: it returns the list, and the filtering is yours to do. The values below are there so you can recognize the topic and the use case of each model in the response.

Topics and use cases

The use cases Meta publishes, by topic: Model names usually end in a number, such as delivery_update_1 or low_balance_warning_1: that is what goes in library_template_name.

Creating from a model

Creation uses the same API reference endpoint, but the body is different: instead of components, you send the model name and the inputs it accepts.
The body text belongs to Meta: you do not write the message, you only turn on or off the sentences the model offers (add_contact_number, add_learn_more_link, add_security_recommendation, add_track_package_link) and provide the data for the buttons it asks for.
A model used as is starts out approved. Meta’s docs say customizing changes that: “If you choose Customize template, your template will have to go through review before you are able to send messages.” If you change the content, it goes back into the normal review queue.

Authorizations

Authorization
string
header
required

Secret Key generated in the Omni Z-API Security panel

Path Parameters

wabaId
string
required

WABA ID (obtained via List WABAs)

Example:

"428083093730937"

Response

Library templates

data
object[]