easyCoexistence
Log inStart Free Trial
Meta Tech Provider

WhatsApp error 100: invalid parameter

Error 100 means the request carried a parameter Meta does not accept: unsupported, misspelled, or the wrong shape for that endpoint. It is deterministic, so the same request fails identically every time and retrying it never helps.

100

Meta's code for an unsupported, misspelled or invalid parameter.

131008

The narrower code for a required parameter that was missing entirely.

131009

The narrower code for a parameter whose value is out of range.

What produces it

Something about the request body or query that the endpoint does not recognise, and the causes are boringly consistent.

  • A field name misspelled, or in the wrong case.
  • A parameter that belongs to a different endpoint.
  • A value of the wrong type, such as a number sent as a string where an integer is expected.
  • A nested object flattened, or a flat value sent where an object belongs.

Why retrying is pointless

Because nothing about the platform changed between attempts. A malformed request is malformed on the second attempt for the same reason it was on the first, and a retry loop around this error produces rate limiting on top of the original problem rather than a success.\n\nThe useful response is to log the request body alongside the error and compare it field by field against the endpoint reference. In almost every case the difference is visible within a minute of looking.

Common mistakes

  • Retrying. The request is deterministic and will fail identically.
  • Assuming it is the number. This error never means anything about the connection.
  • Reading it as a generic failure. It names a parameter problem specifically, and the narrower codes 131008 and 131009 exist for missing and out of range values.
Doing this with EasyCoexistence

EasyCoexistence exposes the credentials and phone number id you need through the dashboard and the MCP connector, so a request is built against the values Meta actually holds rather than ones written down once.

Frequently asked questions

Does this mean my number is broken?

No. This error concerns the request only, and the number is unaffected.

Why is it so vague?

It is the catch all for parameter problems. Meta has narrower codes for a missing parameter and for an invalid value.

Can a provider cause this?

Only by building the request. On a direct integration, the request is yours.

Should I retry with a backoff?

No. It is deterministic, and retrying adds rate limiting to a problem that is not transient.

Keep reading

WhatsApp error 131008: required parameter missingError 131008 means a parameter the endpoint requires was not included. Narrower than error 100, and usually one field away from working.WhatsApp error 131009: invalid parameter valueError 131009 means a parameter was present with a value the endpoint does not accept. Common causes: locale codes, phone formats and enum values.WhatsApp error 132000: parameter count mismatchError 132000 means the number of variables you sent does not match the number the template defines. How to count them and why it appears after an edit.WhatsApp Coexistence: the app and the API on one numberCoexistence runs the WhatsApp Business app and the Cloud API on the same number at once. What it changes, what it does not, and how a number gets connected.WhatsApp Cloud API error codesEvery WhatsApp Cloud API error code in one table: what each one means, whether retrying helps, and the page that covers it in full.

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on

WhatsApp Error 100