Overview
Templates v2 manages the full Meta template lifecycle under /api/v2/whatsapp/templates. Create drafts, submit for Meta review, poll until APPROVED, send to recipients, and delete when obsolete. Prefer v2 for new integrations; pair with v2 media uploads for per-recipient headers.
Template lifecycle
Five core operations cover create, submit, send, read, and delete. Child pages document request parameters and code samples for send and media upload.
Note: Only APPROVED templates can be sent. Attempting to send a DRAFT or PENDING template returns HTTP 400 with the current state in the response.
State transitions
DRAFT → submit → PENDING → APPROVED (minutes to hours) or REJECTED (check data field for reason). APPROVED → send → delivered to recipient. Any state → delete → removed from Buzzbip and Meta.
Integration notes
When integrating the Buzzbip whatsapp endpoint into your application, treat https://app.buzzbip.com as the only production host. Obtain a JWT from POST /api/login_check and send Authorization: Bearer <token> on every request. Confirm User.hasApiAccess is enabled in Buzzbip Admin — without it, valid tokens still receive authorization errors. Parse JSend responses by reading status, message, and data together; do not rely on HTTP status codes alone. For ecommerce plugins, also send x-api-key, x-platform-type, and x-base-uri as described in the secret-key documentation. v2 WhatsApp routes do not use trailing slashes. Implement retries with exponential backoff when you encounter rate limits, and log full error bodies during development. Store credentials server-side, rotate secrets if exposed, and re-authenticate before the 3600-second JWT TTL expires in long-running workers. Queue bulk WhatsApp sends from your backend rather than client browsers. Test against a small set of contacts before enabling production campaigns.
Security
Security best practices for Buzzbip API clients include restricting API credentials to backend services, using TLS for every request, and monitoring failed authentication attempts. Separate staging and production Buzzbip accounts when possible so template tests do not message real customers. Document which templates and automations each integration triggers. When debugging, redact phone numbers and message bodies in application logs shared with third parties.
What's next?
See related operations: api/v2/whatsapp-templates/send-template api/v2/whatsapp-media guides/whatsapp-v2-use-cases guides/create-whatsapp-template