Marketing Messages
MM API Error Code List
The Marketing Messages (MM) API for WhatsApp uses the same core error codes as the Cloud API, with several additional error codes specific to its advertising and campaign-based architecture. These additional errors primarily relate to message type restrictions, template synchronisation with Meta Ads, and onboarding eligibility.
⚠️⚠️ Note: These errors are only relevant if you are using the Marketing Messages Lite API endpoint
Error 100 Only Template Message
(MM API) - Invalid Parameter - Message Must Be a Template Message
ERROR CODE
100 (MM API)
ERROR SUMMARY
Invalid Parameter — Message Must Be a Template Message
ERROR DESCRIPTION
When using the Marketing Messages API, only template messages are permitted. Attempting to send a free-form text message, media message, or any other non-template message type will result in this error.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. Switch from a non-template message type to a template message type in your API request.
2. Ensure the 'type' field in the message object is set to 'template'.
3. Include the required 'template' object with the 'name', 'language', and 'components' fields.
OTHER NOTES
The MM API is designed specifically for marketing campaigns using approved templates. It is not a general-purpose messaging endpoint.
Error 131009 Invalid Parameters
MM API - Parameter Value Not Valid — Invalid Parameter or Incomplete Ad Sync
ERROR CODE
131009 (MM API)
ERROR SUMMARY
Parameter Value Not Valid — Invalid Parameter or Incomplete Ad Sync
ERROR DESCRIPTION
A parameter value is invalid in the MM API context. This may be due to an invalid parameter format or because the ad synchronisation for the template has not yet completed. Ad synchronisation can take up to 10 minutes after a template is created or modified.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. Verify all parameters against the MM API documentation at https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/send-marketing-messages.
2. If the template was recently created or modified, wait 10 minutes for ad synchronisation to complete before retrying.
3. If the issue persists after 10 minutes, contact Meta Support.
OTHER NOTES
Ad synchronisation is unique to the MM API — standard Cloud API templates do not require this step. Always allow sufficient time for sync after template changes.
Error 131055 Only Marketing
Method Not Allowed — Only Marketing Templates Supported
ERROR CODE
131055
ERROR SUMMARY
Method Not Allowed — Only Marketing Templates Supported
ERROR DESCRIPTION
The MM API does not support the template category being sent. Only templates categorised as 'MARKETING' can be sent via the MM API. Attempting to send an Authentication or Utility template will trigger this error.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. If you need to send a Utility or Authentication template, use the standard Cloud API messages endpoint instead.
2. Verify the template category — ensure the template you are sending is categorised as 'MARKETING' in WhatsApp Manager.
3. Do not attempt to recategorise non-marketing templates as marketing to bypass this restriction.
OTHER NOTES
Using the correct API endpoint for the correct template category is important. The MM API is specifically optimised for marketing use cases.
Error 132018 Parameters Issue
Template Validation Error - Issue with Template Parameters
ERROR CODE
132018
ERROR SUMMARY
Template Validation Error — Issue with Template Parameters
ERROR DESCRIPTION
There is a validation error with one or more parameters in the template message within the MM API context. This is a more specific template validation error used by the MM API.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. Review the error response for details on which parameters have issues.
2. Correct the parameter values and formats according to the error details.
3. Resend the message with corrected parameters.
OTHER NOTES
The MM API has additional parameter validation requirements beyond the standard Cloud API. Refer to the MM API-specific documentation for exact parameter specifications.
Error 134100 Only Marketing
Only Marketing Messages Supported
ERROR CODE
134100
ERROR SUMMARY
Only Marketing Messages Supported
ERROR DESCRIPTION
Available with Graph API version 23.0 and later. You are attempting to send a Utility or Authentication template via the MM API, which exclusively supports Marketing category templates.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. Use the standard Cloud API for sending Utility or Authentication templates.
2. Ensure templates sent via MM API are categorised as 'MARKETING'.
OTHER NOTES
This error code is available from Graph API v23.0 onwards and provides a more explicit version of the restriction previously returned as Error 131055.
Error 134101 — Template Is Still Syncing
ERROR CODE
134101
ERROR SUMMARY
Template Is Still Syncing
ERROR DESCRIPTION
Available with Graph API version 23.0 and later. You are attempting to send a newly created template before its ad synchronisation process has completed. Ad sync can take up to 10 minutes.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. Wait 10 minutes after creating or modifying a template before attempting to send it via the MM API.
2. Implement a delay and retry mechanism in your campaign dispatch logic.
OTHER NOTES
This more specific error code (compared to 131009) makes it easier to identify sync-related vs. other parameter validation issues. Available from Graph API v23.0.
Error 134102 Template Unavailable
Template Unavailable for Use - Ad Sync Failed or Ineligible Account
ERROR CODE
134102
ERROR SUMMARY
Template Unavailable for Use — Ad Sync Failed or Ineligible Account
ERROR DESCRIPTION
Available with Graph API version 23.0 and later. The template cannot be used, either because ad synchronisation failed or because the WABA is not eligible for the Marketing Messages API.
HTTP Status: 500 Internal Server Error.
RESOLUTION & TROUBLESHOOTING STEPS
1. Check your WABA's MM API eligibility status by querying the 'marketing_messages_lite_api_status' field.
2. If the status is 'ONBOARDED' and the problem persists, contact Meta Direct Support.
3. If the status is not 'ONBOARDED', follow the MM API onboarding process at https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/onboarding.
OTHER NOTES
The MM API has a separate onboarding process from the standard Cloud API. WABAs must be explicitly onboarded to use the MM API.
Error 1752041 - Already Invited
Duplicate Request — Client Already Invited to Onboard
ERROR CODE
1752041
ERROR SUMMARY
Duplicate Request — Client Already Invited to Onboard
ERROR DESCRIPTION
An onboarding request for this business customer has already been submitted by another partner. The MM API onboarding process is limited to one request per business customer — only the first partner to call the intent API can submit the request.
HTTP Status: 400 Bad Request.
RESOLUTION & TROUBLESHOOTING STEPS
1. If you receive this error, no further action is needed on your part. All eligible WABAs for the client are included in the onboarding process initiated by the first partner.
2. If you are the correct partner and believe this is an error, contact Meta Support.
3. Do not resubmit the onboarding intent — doing so will not change the outcome.
OTHER NOTES
This safeguard prevents multiple partners from onboarding the same client, which could cause conflicts. The first partner submission takes precedence and covers all eligible WABAs.