Skip to content
Meta Business PartnerAPI error reference

WhatsApp API errors 1 and 2: unknown error or temporary downtime

Codes 1 and 2 are the platform's most general errors. Code 1 can mean a malformed request or a server error; code 2 means the service was temporarily down or overloaded.

1, 2
Codes
API unknown
Meta's name
Meta service
Type
On the API response
Where you see it
Yes, with backoff
Retry

Quick answer

Check Meta's platform status first. With no outage, code 1 usually means the request needs checking; code 2 clears with patient retries.

What WhatsApp error 1 means

Meta documents code 1 as: invalid request or possible server error. It advises checking the WhatsApp Business Platform status page and, if there's no outage, checking the request format against the endpoint reference. It documents code 2 as: temporary, due to downtime or being overloaded, and advises checking the status page before trying again.

Why error 1 happens

This one starts on Meta's side, though your request can play a part. Likely causes:

  • A malformed request, such as invalid JSON or a wrong endpoint path (code 1).
  • A server-side error at Meta (code 1).
  • Temporary downtime or overload on the platform (code 2).
  • A request sent to an endpoint path with a typo or the wrong API version.

How to fix error 1

Most of the work is making your sending resilient so this resolves itself.

  • Check the WhatsApp Business Platform status page.
  • For code 1 with no outage, validate the request: JSON, endpoint path and required fields.
  • For code 2, retry with exponential backoff and jitter.
  • Log the trace IDs; if errors persist without an outage, contact support.
  • Compare the failing request with the endpoint reference, including the API version in the path.

Should you retry after 1?

Retry code 2 with backoff. Retry code 1 only after confirming the request is valid, since a malformed request fails every time.

How error 1 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 1, a message beginning "(#1)" 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

How do I tell a bad request from a server error with code 1?+
Check the platform status page. If there's no incident and the same request fails every time, the request is the problem; if failures are intermittent, it's more likely server-side.
Is code 2 the same as 131016?+
Both describe temporary unavailability. Code 2 is a general platform code for downtime or overload; 131016 is WhatsApp's own service-unavailable error. Handle both with backoff.
Should I alert on codes 1 and 2?+
Alert on a spike rather than single errors. A burst of code 2 across many sends usually lines up with a platform incident.

Retries handled, failures explained

InfiQ returns Meta's error with its own trace ID and posts failures to your webhook, so outages don't lose messages silently.