WhatsApp template JSON generator

The JSON generator builds the template payload developers paste into the WhatsApp API or into a server-side send call.

The inbox UI is enough for many teams. A developer sending order alerts from WooCommerce, a billing system, or an internal tool needs the JSON body the API expects: the template name, the language code, and the parameters in the right order. A mismatch here is a common reason a template that looks approved still fails at send time.

Use the generator to assemble that body from the template you already wrote. Check the language, the button parameters, and the header or body variables. Compare it with the approved template name in WhatsApp Manager before you put it in production code. The generator does not submit the template to Meta and it does not send the message.

Keep secrets out of the JSON you share. The payload should contain the template structure and sample parameters, not a permanent access token. Rotate any token that has been pasted into a ticket or a chat.

Once the JSON matches the approved template, Bulkwise can send it from the shared inbox or from an automation your developer connects. The software plan is separate from Meta’s conversation fees. Starter is ₹2,500 a month and Growth is ₹3,500 a month. Setup takes 3 to 5 business days, including Meta verification.

Open the JSON generator to prepare the payload. Start a free trial when the send should run inside Bulkwise, or book a demo if a developer on your side wants the endpoint walked through on a call.

Match every placeholder to a parameter, in the same order the approved template uses. A body with three variables and a payload with two will fail even when the template name is correct. Buttons that open a website need the URL you registered, not a new URL invented at send time, unless the template was created with a dynamic suffix. Language codes are part of the name lookup: an English India template is not the same object as an English US template. Send one test to your own number, confirm the variables landed in the right places, and only then point the job at a customer list. Keep that test send in your notes so the next developer can see a known-good body. Store the payload next to the template name in your repo, and change it only when Meta approves a new version of that same template.