WhatsApp error 133010: Phone number Not Registered

Code 133010 means the business phone number you are using as the sender is not registered with the Cloud API, so it cannot send or receive messages. A number can exist in your WABA, show up in WhatsApp Manager, have a verified display name, and still not be registered: registration is the explicit POST /{phone-number-id}/register call with your two-step PIN that activates the number on the platform. Until that call succeeds, any /messages request from that number returns 133010.

It is one of the first errors developers meet after moving from the test number (which Meta registers for you) to a real number (which you must register yourself). It also reappears after a deregistration, a migration from the WhatsApp Business app or On-Premises API, or when a number is moved to a new WABA.

Your token, template, and recipient can all be perfect. The sender simply is not switched on.

133010 is synchronous and specific to the sender: the platform refuses the call before creating a message, so there is nothing to watch for in webhooks. Gotchas worth knowing: the App Dashboard test number never hits this error because Meta pre-registers it, so the first 133010 typically lands on go-live day; and registration state is tied to the phone number ID, so a number migrated to a new WABA gets a new ID that starts unregistered even though the old one was CONNECTED (131045 is the send-time variant of the same state). Registering on the Cloud API also severs the number from the consumer WhatsApp or WhatsApp Business app - the two cannot hold the number simultaneously. If you onboard through a BSP, registration is normally performed by the provider during embedded signup, so a 133010 on a 360dialog or Interakt number is a ticket to the provider rather than a register call you should make yourself. The full setup sequence, with the errors each step can throw, is walked through in the registration troubleshooting guide, and the registration attempt ceilings live in the limits reference.

{
  "error": {
    "message": "(#133010) Phone number Not Registered",
    "type": "OAuthException",
    "code": 133010,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "Phone number not registered on the WhatsApp Business Platform."
    },
    "fbtrace_id": "AqWeRtYuIoP1234"
  }
}

Make registration an explicit, verified step in onboarding and in any migration runbook, with a post-step check that status is CONNECTED. Add the same check to a periodic health monitor so an unexpected deregistration is caught within minutes. Keep the PIN in a secrets manager so registration can be repeated without hunting for it.