WhatsApp error 134102: Template unavailable for use
Last verified against Meta for Developers - Cloud API error codes
Please check your eligibility status to ensure you are onboarded or contact Meta's customer support.What error 134102 means
Code 134102 comes back from /marketing_messages with HTTP 500. Meta gives two explanations: ad synchronization could not be completed for the template, or the account may not be eligible for the MM API. Despite the 500 status, this is usually not a transient server fault to retry blindly.
Eligibility is visible through the API. Meta's onboarding guide uses the marketing_messages_onboarding_status field on the WABA, where ELIGIBLE means the account can onboard and ONBOARDED means it already has. The older marketing_messages_lite_api_status field, which the error reference still mentions, is slated for deprecation. Meta's guidance: if the status shows the account is onboarded and the problem persists, contact support.
Compare with 134101, where sync is merely still running. 134102 means it failed or cannot happen.
What it looks like
{
"error": {
"message": "(#134102) Template unavailable for use",
"type": "OAuthException",
"code": 134102,
"error_data": {
"messaging_product": "whatsapp",
"details": "Please check your eligibility status to ensure you are onboarded or contact Meta's customer support."
},
"fbtrace_id": "AqZ3wE5rT7yU9iO"
}
}Why it happens
- The WABA has not completed MM API onboarding, including the terms of service.
- The account is not eligible for the MM API.
- Ad synchronization for this specific template failed.
- Legacy OBO-model accounts that were never transferred to the client.
How to fix WhatsApp error 134102
- 1Query
GET /<WABA_ID>?fields=marketing_messages_onboarding_statusand read the value. - 2If it is
ELIGIBLErather thanONBOARDED, finish onboarding and accept the MM API terms in WhatsApp Manager. - 3If the account is onboarded, try a different approved marketing template to see whether the failure is template-specific.
- 4If it persists on an onboarded account, open a Direct Support case with the fbtrace_id.
How to stop it recurring
Check onboarding status per WABA before routing any traffic to /marketing_messages, and keep the default CLOUD_API_FALLBACK product policy unless you have a reason to use STRICT, so marketing sends from not-yet-onboarded accounts still go out through Cloud API.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
- 134101: Your template is still syncingWhen you send a message from a template, the template syncing process can take…
- 131063: Marketing templates disabled for Cloud APIYour template is categorized as Marketing, but marketing templates are…
- 131055: Method not allowedOnly marketing template messages are supported
- 1752041: Duplicate RequestDuplicate Request is thrown when a client has already been invited to onboard…
Error 134102 - quick answers
What does WhatsApp error 134102 mean?
Code 134102 comes back from /marketing_messages with HTTP 500. Meta gives two explanations: ad synchronization could not be completed for the template, or the account may not be eligible for the MM API. Despite the 500 status, this is usually not a transient server fault to retry blindly. Eligibility is visible through the API.
How do I fix WhatsApp error 134102?
1. Query GET /<WABA_ID>?fields=marketing_messages_onboarding_status and read the value. 2. If it is ELIGIBLE rather than ONBOARDED , finish onboarding and accept the MM API terms in WhatsApp Manager. 3. If the account is onboarded, try a different approved marketing template to see whether the failure is template-specific. 4. If it persists on an onboarded account, open a Direct Support case with the fbtrace_id.
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.