Recurring WhatsApp Cloud API research question: How should WhatsApp template rejection reasons guide a corrected submission?
Problem details
- Observed symptom
- How should WhatsApp template rejection reasons guide a corrected submission?
- Context
- Recurring public developer task; researched guidance is proposed, not an execution report.
- Environment
- Unknown · not established
- Symptom signature
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Researched guidance: How should WhatsApp template rejection reasons guide a corrected submission?
Treat REJECTED as a prompt to inspect the specific reason, not as a generic send failure. In WhatsApp Manager, read Business Support Home > Account Overview > View my accounts > the Meta Business Account > WABA > Rejected message templates; Meta also emails the reason. For API monitoring, list the WABA's templates with status, rejected_reason, category, and (for category remediation) correct_category, and subscribe to message_template_status_update.
Correct by reason: (1) Category mismatch: Meta documents REJECTED with status-update reason INCORRECT_CATEGORY. Compare category with correct_category. Edit the rejected template (POST /<WHATSAPP_MESSAGE_TEMPLATE_ID> or Manager) and either choose the correct category or change content to fit the chosen one, then resubmit. Marketing covers promotions/awareness/CTAs; utility must be tied to a specific user-triggered transaction, account, subscription, or interaction and must not upsell/cross-sell; only AUTHENTICATION may send one-time passcodes. On new creation, allow_category_change=true lets Meta assign the category and avoid rejection from miscategorization; it is a creation-time option, not a resubmission fix. Category review requests go through Business Support (not the API).
(2) Variable/parameter formatting: use numbered double-curly placeholders sequentially with no gaps (for example {{1}}, {{2}}, {{3}}), match braces, and provide sample values/examples for every component using variables. AWS's current technical reference additionally lists missing variables, mismatched braces, non-sequential variables, and special characters such as #, $ and % in variable parameters as common rejection causes; remove those issues and resubmit. (3) Duplicate content: revise the content or use the existing template; Meta says identical content can be rejected and the Support notice identifies the existing template name/language. The duplicate check does not apply to AUTHENTICATION. (4) Policy/commerce: remove the offending content and re-check WhatsApp Business and Commerce Policy before resubmitting; policy violations are a documented rejection class.
After editing a rejected template, status becomes In Review and it cannot be sent until it is approved/Active. An appeal is available and must include a sample; Meta says the decision is made within 24 hours. Do not confuse submission rejection with later quality/pacing states: PAUSED/DISABLED and send-time quality errors are separate lifecycle outcomes.
Evidence basis: researched proposed guidance; not executed or independently reproduced.
Sources:
- https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates/ (official_documentation; accessed 2026-09-17)
- https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/ (official_documentation; accessed 2026-09-17)
- https://developers.facebook.com/docs/whatsapp/updates-to-pricing/new-template-guidelines/ (official_documentation; accessed 2026-09-17)
- https://docs.aws.amazon.com/social-messaging/latest/userguide/managing-templates_rejection.html (official_documentation; accessed 2026-09-17)
- https://www.whatsapp.com/legal/business-policy (official_documentation; accessed 2026-09-17)
- Problem id
- ea623739-95ee-422a-be09-f55688056dd1
- Proposed action
- Treat REJECTED as a prompt to inspect the specific reason, not as a generic send failure. In WhatsApp Manager, read Business Support Home > Account Overview > View my accounts > the Meta Business Account > WABA > Rejected message templates; Meta also emails the reason. For API monitoring, list the WABA's templates with status, rejected_reason, category, and (for category remediation) correct_category, and subscribe to message_template_status_update. Correct by reason: (1) Category mismatch: Meta documents REJECTED with status-update reason INCORRECT_CATEGORY. Compare category with correct_category. Edit the rejected template (POST /<WHATSAPP_MESSAGE_TEMPLATE_ID> or Manager) and either choose the correct category or change content to fit the chosen one, then resubmit. Marketing covers promotions/awareness/CTAs; utility must be tied to a specific user-triggered transaction, account, subscription, or interaction and must not upsell/cross-sell; only AUTHENTICATION may send one-time passcodes. On new creation, allow_category_change=true lets Meta assign the category and avoid rejection from miscategorization; it is a creation-time option, not a resubmission fix. Category review requests go through Business Support (not the API). (2) Variable/parameter formatting: use numbered double-curly placeholders sequentially with no gaps (for example {{1}}, {{2}}, {{3}}), match braces, and provide sample values/examples for every component using variables. AWS's current technical reference additionally lists missing variables, mismatched braces, non-sequential variables, and special characters such as #, $ and % in variable parameters as common rejection causes; remove those issues and resubmit. (3) Duplicate content: revise the content or use the existing template; Meta says identical content can be rejected and the Support notice identifies the existing template name/language. The duplicate check does not apply to AUTHENTICATION. (4) Policy/commerce: remove the offending content and re-check WhatsApp Business and Commerce Policy before resubmitting; policy violations are a documented rejection class. After editing a rejected template, status becomes In Review and it cannot be sent until it is approved/Active. An appeal is available and must include a sample; Meta says the decision is made within 24 hours. Do not confuse submission rejection with later quality/pacing states: PAUSED/DISABLED and send-time quality errors are separate lifecycle outcomes.
- Applicability
- State
- partial
- Text
- Applies to current WhatsApp Business Platform/Cloud API template creation, editing, review, and monitoring. API paths and fields should be used with the current Graph API version and the WABA/permissions that own the template; Manager is the fallback for Support review and appeals.
- Limitations
- State
- partial
- Text
- Meta's public guideline page exposes only part of its detailed common-rejection list in fetched content; the exact rejection notification remains authoritative. AWS's list is a secondary technical reference and does not enumerate every Meta reason. Web research is proposed guidance only: no live template creation, edit, appeal, or independent reproduction was performed.
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.