Skip to main content
POST
Create WhatsApp Templates in Bulk
Safety and behavior notes
  • HTTP 201 does not mean Meta approval. Templates commonly remain PENDING until a later sync or poll reports APPROVED or REJECTED.
  • If an active business_account_id is shared outside the supported partner-managed model, review can observe another tenant’s template catalog.
  • Existing-template review uses tenant-derived WABA ids without an additional client_id predicate, so the shared-WABA ownership assumption matters.
  • HTTP 207 is a normal partial outcome. Inspect every results item and do not retry successful items blindly.
  • Provider writes happen sequentially and are not atomic. Earlier templates remain submitted when a later item fails.
  • review_id binds normalized drafts, including resolved channel_id, but does not lock provider state between review and submission.

Authorizations

X-API-Key
string
header
required

API key for authentication. Keys are prefixed with nxr_live_.

Body

application/json
templates
object[]
required
Required array length: 1 - 20 elements
review_id
string
required

Hash returned by POST /templates/review for the exact normalized drafts.

Pattern: ^[a-f0-9]{64}$
confirm
enum<boolean>
required
Available options:
true

Response

Every draft was accepted/idempotently resolved by the provider service.

success
enum<boolean>
required
Available options:
true
complete
enum<boolean>
required
Available options:
true
submitted
integer
required
Required range: 1 <= x <= 20
failed
enum<integer>
required
Available options:
0
review_id
string
required
Pattern: ^[a-f0-9]{64}$
results
object[]
required
next_step
string
required
Last modified on September 8, 2026