Template responses now include category

Released: August 10, 2026

category is now returned on template reads Added

You could always submit a category when creating a template (POST /v1/{phone_number_id}/templates), but the value was not returned when you read templates back — an asymmetry that made it impossible to tell a template’s category from the API alone.

Both read endpoints now include a category field:

• GET /v1/{phone_number_id}/templates
• GET /v1/{phone_number_id}/templates/{name}

{
  "id": "tmpl_01HXYZ…",
  "object": "template",
  "name": "order_update",
  "language": "id",
  "status": "approved",
  "category": "UTILITY",
  "content": "Pesanan {{1}} sedang diproses.",
  "…": "…"
}

The value is one of MARKETING, UTILITY, or AUTHENTICATION.

Note

category is null only for templates synced before this field was recorded. Running POST /v1/{phone_number_id}/templates/sync backfills it from Meta.

The TypeScript SDK surfaces the same field on Template and template list items — upgrade to the latest version to read template.category.

API reference — List templates → Create templates