WhatsApp Templates API

2. Authentication & scopes

Public Developer API for Meta template lifecycle on Cloud WhatsApp accounts. Same Meta engine as the Washeej dashboard. Access requires explicit template scopes; Device/QR management is rejected. Provider Meta delete stays deferred.

1. Overview

2. Authentication & scopes

3. Account capabilities

4. Validate a template

5. Create and submit

6. List and inspect status

7. Sync

8. Edit

9. Delete

10. Send approved template

11. Status webhooks

12. Error codes

13. Rate limits

14. Idempotency

15. Migration from /templates/send

Auth

Use API key authentication (client-id / client-secret + IP whitelist) or OAuth 2.0 (Connect with Washeej). Washeej resolves Meta tokens — never send WABA secrets.

Scopes

templates:read — list, detail, validate, capabilities (validate is local-only; still requires lifecycle enablement)
templates:write — create, edit, delete (explicit; not auto-granted to legacy null keys)
templates:sync — sync (explicit)
messages:send — send (templates:send is not accepted on this route)
messages:webhook — register endpoints
account:read / whatsapp_accounts:read — account listing

Missing scope → 403 insufficient_scope. Feature not assigned → 403 feature_disabled.