WhatsApp API error 134102: Template unavailable for use
Error 134102 means the template can't be used on the Marketing Messages API. Either its synchronisation for marketing sends couldn't complete, or the account isn't eligible for that API.
Quick answer
The template can't be used for marketing sends. Check the account's Marketing Messages API onboarding status; if it's onboarded and the error continues, contact Meta support.What WhatsApp error 134102 means
Meta documents 134102, "Template unavailable for use", with HTTP 500: ad synchronisation couldn't be completed for the template, or you may not be eligible for the Marketing Messages API. Its advice is to check your eligibility status, and if the WhatsApp Business Account's marketing_messages_lite_api_status is ONBOARDED and the problem continues, to contact support. Meta lists it as available from Graph API v23.0.
Why error 134102 happens
This code belongs to Meta's Marketing Messages API, so the cause sits in how marketing sends are routed or set up. Typically:
- The account isn't onboarded to the Marketing Messages API.
- The template's synchronisation for marketing sends failed.
- Eligibility for the API changed for the account.
How to fix error 134102
Work through these in order; the first one that turns up a problem is usually the fix.
- Check the account's onboarding status for the Marketing Messages API.
- If it isn't onboarded, complete onboarding or send the template through the Cloud API meanwhile.
- If it is onboarded, wait a little and retry once, then contact Meta support with the details.
- Keep a fallback route for important marketing sends while this is investigated.
Should you retry after 134102?
One retry after a short wait is reasonable because sync problems can clear. If it persists on an onboarded account, contact support rather than retrying.
How error 134102 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 134102, the "(#134102)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.