Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 131009: Parameter value is not valid

Error 131009 means a field in the request is there, but the value in it isn't one WhatsApp accepts. It is one of the most common request errors and almost always comes with details naming the field.

131009
Code
Parameter value is not valid
Meta's name
Request
Type
400
HTTP status
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

One of the values you sent isn't valid. Use the error details to find which field, correct the value to one the API supports, and resend.

What WhatsApp error 131009 means

Meta documents 131009 as: one or more parameter values are invalid, with HTTP status 400. Meta points to the endpoint reference for supported values, and to adding the phone number to the WhatsApp Business Account when the sender number is the problem. For newly created marketing templates Meta also notes that ad syncing may be incomplete, so waiting about 10 minutes can help.

Why error 131009 happens

Request errors come from the payload, so the cause is usually in how it was built. Look for these first:

  • A recipient number that isn't in international format, or has spaces, brackets or a leading zero.
  • A sending number that isn't added to, or registered in, the WhatsApp Business Account.
  • An unsupported value, such as an unknown message type, language code or button type.
  • A media link that isn't a valid public HTTPS URL.
  • A marketing template sent within minutes of creation, before Meta finished syncing it.

How to fix error 131009

Work through these in order; the first one that turns up a problem is usually the fix.

  • Read the details text to see which field was rejected.
  • Normalise phone numbers to E.164 digits with the country code and no symbols before sending.
  • Check that the sending number belongs to the account you are sending from and is registered.
  • Compare enumerated values, such as type and language, with the supported list.
  • For a brand-new marketing template, wait around 10 minutes and try again.

Should you retry after 131009?

Correct the value and resend. Retry without changes only for the new-template syncing case, after a short wait.

How error 131009 shows up in InfiQ

If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 131009, a message beginning "(#131009)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.

Send it through InfiQ

Frequently asked questions

Does error 131009 mean the phone number is wrong?+
Often, but not always. Check the recipient number's format first, then the sending number's registration, then the other fields named in the error details.
Why does a new template return 131009?+
Meta notes that ad syncing may be incomplete for a newly created template used through the marketing messages route. Waiting about 10 minutes before the first send usually resolves it.