WhatsApp Cloud API - Template API | Developer Documentation

Fetch approved WhatsApp templates with the ChatArchitect API

Use this reference when your application needs a selectable list of approved templates for a connected ChatArchitect account. The ChatArchitect API quick start documents /getHSM and the returned send string. Creation and changes in the cabinet are covered by the template-management guide.

Authenticate and request the list

Send JSON to POST https://api.chatarchitect.com/getHSM from your server. Use Basic Auth with APP_ID as username and APP_SECRET as password, using the issued values for the intended connection. The credentials guide covers App key/Secret; keep both out of browser code and public logs.

The documented request body is:

{
  "channel": "whatsapp",
  "destination": "<recipient_phone>",
  "getHSM": "true"
}

Keep getHSM as the string "true" shown in the guide. Its example uses a phone destination in international digits without a plus sign, spaces or brackets. Use the value applicable to your connection according to the current guide; if the intended destination for the list request is unclear, confirm it with support before calling.

This operation retrieves a template list. It does not send a WhatsApp message.

Read the returned list

This is a reduced, illustrative response fragment. The identifiers are example values and must not be used for an actual send.

{
  "status": "submitted",
  "templates_status": true,
  "templates": [
    {
      "appId": "00000000-0000-4000-8000-000000000001",
      "category": "MARKETING",
      "data": "{{00000000-0000-4000-8000-000000000002}}\nHello{{1}}"
    }
  ]
}

Do not manufacture a language, status, name or quality field absent from this fragment. Review the actual response and confirm additional fields before depending on them. The list response does not require a delivery event as evidence of a customer send.

Select the template and fill its variables

1. Select an approved entry for the intended recipient and purpose. Show its returned category and text preview for review.
2. Keep the first {{template_id}} block in data. A name or appId does not replace that send prefix.
3. Map numbered variables such as {{1}} and {{2}} to the intended values in their original order. Values can contain spaces and multiple words, but no line breaks.
4. Preserve the separator after the prefix. In JSON, a newline is represented as \n; copying a displayed string must preserve its actual content.
5. Review the recipient and complete message before using /whatsappmessage. The send reference covers the request and later delivery outcome.

Use the component guide to review text, variables and supported buttons. A returned category does not establish OTP delivery, media headers or every Meta button type as a supported ChatArchitect scenario.

Refresh after a change or missing entry

Your application can retain the list for selection as described in the quick start. Offer a deliberate refresh and retain the response time/connection. The guide does not specify a cache lifetime or automatic synchronization guarantee.

After editing or deleting a template in wtargeted.com, obtain a fresh list and review the selection before another send. Confirm behavior for already prepared or queued messages with the responsible tool; an old cached entry or local preview may be outdated.

• Check that the issued credentials and requested connection are the intended ones.
• Review approval and availability in the cabinet, then inspect a new list response.
• If the entry is still missing, retain the request time and redacted response for support. Do not use a guessed ID or another account's template.

Meta's Template API reference covers its direct provider interface. The ChatArchitect quick start documents list retrieval and sending, but does not provide create, edit or delete API endpoints for templates. Use the supported cabinet workflow and confirm any additional API operation before implementing it.