Anleitungen

Buzzbip Anleitung — Häufige WhatsApp-API-Fallen

Acht WhatsApp-Integrationsfallen bei Buzzbip: Telefonformat, Slashes, Vorlagenstatus, body_params, URLs, Medienbereich, Anhänge und Zustellbestätigungen.

Übersicht

Acht häufige Fehler bei der Integration der Buzzbip WhatsApp API, jeweils mit der genauen Lösung. Lesen Sie dies vor dem Produktivgang.

Die 8 häufigen Fallstricke

Die Tabelle listet jedes Problem, typisches Symptom und Lösung. Tabellen bleiben auf Englisch zum Debuggen.

Parameter	Type	Required	Description
`Phone number has + or spaces`	`HTTP 400, "phone_number is not valid"`	Optional	Pass digits only in to. Use country_code for country. Example: "to": "21696816277", "country_code": "TN"
`Trailing slash on v2 endpoint`	`404 or route not matched`	Optional	v1 endpoints (/api/whatsapp/…) require trailing slash. v2 endpoints (/api/v2/whatsapp/…) do NOT. Copy paths exactly from the API reference.
`Sending a non-APPROVED template`	`HTTP 400 with current state in response`	Optional	Check GET /api/v2/whatsapp/templates/{id} before sending. Only state APPROVED can be sent.
`body_params count mismatch`	`HTTP 400, parameter validation error`	Optional	Count {{1}}, {{2}}… in your template body. Provide exactly that many strings in body_params.
`Multiple URL placeholders`	`Template rejected by Meta`	Optional	Meta allows only one {{1}} at the end of a URL. You cannot use patterns like {{1}}/order/{{2}}.
`Cross-tenant media_id`	`HTTP 403 or media not found`	Optional	media_id values are user-scoped. Upload the file while authenticated as the user account that will send the message.
`Multiple PDFs in one send`	`Can only attach one file per message`	Optional	Three options — merge PDFs server-side, send multiple messages, or put extra files behind signed URL buttons.
`Expecting delivery receipts in the API response`	`No read/delivered status in send response`	Optional	Delivery and read receipts arrive via your POST /webhook callback configured in Meta Business Manager, not in the send API response.

Wie geht es weiter?

Verwandt: guides/whatsapp-v2-use-cases api/v2/whatsapp-templates/send-template getting-started/errors

Was this helpful?

Anleitungen

Buzzbip Anleitung — Häufige WhatsApp-API-Fallen

Acht WhatsApp-Integrationsfallen bei Buzzbip: Telefonformat, Slashes, Vorlagenstatus, body_params, URLs, Medienbereich, Anhänge und Zustellbestätigungen.

Übersicht

Acht häufige Fehler bei der Integration der Buzzbip WhatsApp API, jeweils mit der genauen Lösung. Lesen Sie dies vor dem Produktivgang.

Die 8 häufigen Fallstricke

Die Tabelle listet jedes Problem, typisches Symptom und Lösung. Tabellen bleiben auf Englisch zum Debuggen.

Parameter	Type	Required	Description
`Phone number has + or spaces`	`HTTP 400, "phone_number is not valid"`	Optional	Pass digits only in to. Use country_code for country. Example: "to": "21696816277", "country_code": "TN"
`Trailing slash on v2 endpoint`	`404 or route not matched`	Optional	v1 endpoints (/api/whatsapp/…) require trailing slash. v2 endpoints (/api/v2/whatsapp/…) do NOT. Copy paths exactly from the API reference.
`Sending a non-APPROVED template`	`HTTP 400 with current state in response`	Optional	Check GET /api/v2/whatsapp/templates/{id} before sending. Only state APPROVED can be sent.
`body_params count mismatch`	`HTTP 400, parameter validation error`	Optional	Count {{1}}, {{2}}… in your template body. Provide exactly that many strings in body_params.
`Multiple URL placeholders`	`Template rejected by Meta`	Optional	Meta allows only one {{1}} at the end of a URL. You cannot use patterns like {{1}}/order/{{2}}.
`Cross-tenant media_id`	`HTTP 403 or media not found`	Optional	media_id values are user-scoped. Upload the file while authenticated as the user account that will send the message.
`Multiple PDFs in one send`	`Can only attach one file per message`	Optional	Three options — merge PDFs server-side, send multiple messages, or put extra files behind signed URL buttons.
`Expecting delivery receipts in the API response`	`No read/delivered status in send response`	Optional	Delivery and read receipts arrive via your POST /webhook callback configured in Meta Business Manager, not in the send API response.

Wie geht es weiter?

Verwandt: guides/whatsapp-v2-use-cases api/v2/whatsapp-templates/send-template getting-started/errors

Was this helpful?

Buzzbip Anleitung — Häufige WhatsApp-API-Fallen

Übersicht

Die 8 häufigen Fallstricke

Wie geht es weiter?

Need help with your integration?

Buzzbip Anleitung — Häufige WhatsApp-API-Fallen

Übersicht

Die 8 häufigen Fallstricke

Wie geht es weiter?

Need help with your integration?