Skip to main content

What it does

Returns the current detail of a single template (by Meta sourceId). Data is read fresh directly from Meta (no caching); the app_id is verified to belong to the organization. With expand=components, the body/header/button details are included too.

Endpoint

Headers

string
required
Secret key in Bearer sk_... format. See Secret Key authentication.

Path parameters

string
required
Application ID. Must belong to the organization.
string
required
The template’s Meta ID.

Query parameters

string[]
components → also returns the components. Default: metadata only. See Template Expand.

Response

Type: Result[TemplateResponseModel] (single). The envelope is { "data": { ... }, "isSuccess": true }.
boolean
true when the request completed successfully.
object

component button object

Each item in a BUTTONS component’s buttons array — also used by carousel card buttons.
string
URL, PHONE_NUMBER, QUICK_REPLY, COPY_CODE, or OTP.
string
The label shown on the button.
string
URL buttons: the target link, possibly containing {{1}}.
string
PHONE_NUMBER buttons. Meta returns it in RFC3966 form (tel:+90-555-123-45-67), not the E.164 form you sent.
string[]
The dynamic-URL sample, or the COPY_CODE coupon code.
string
OTP buttons only: the OTP delivery mode.
string
ONE_TAP / ZERO_TAP autofill label.
string
ONE_TAP / ZERO_TAP Android package name.
string
ONE_TAP / ZERO_TAP Android signature hash.
boolean
ZERO_TAP terms acceptance flag.
Null fields (id, createdAt, updatedAt, messageSendTtlSeconds, correctCategory, previousCategory) are dropped from the response.

Examples

The offer comes back as its own LIMITED_TIME_OFFER component, separate from the body and buttons.

Errors

object
Error details with code, group, and description; isSuccess is false.

Auth / tenant

Request validation (422)

Meta-side