Messenger Platform · error code

Messenger error 200: Phone matching access fee required

ConfigurationPermissions, app review & thread control

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Requires phone matching access fee to be paid by this page unless the recipient user is an admin, developer, or tester of the app.

What error 200 means

Code 200 with subcode 2018021 relates to customer matching, the Messenger feature that lets a Page start a conversation by sending to a phone number instead of a Page-scoped ID. The message is self-explanatory: "Requires phone matching access fee to be paid by this page unless the recipient user is an admin, developer, or tester of the app."

That sentence describes two separate gates. App roles: people with a role on your app can be matched by phone number for testing without the fee. Everyone else: the Page needs the paid access in place before phone-number sends go through. Meta's error-codes table does not document the fee amount or the purchase flow, so do not assume a price or a self-serve path; check your Page's options and Meta's current customer matching documentation.

This is distinct from 200/2018027, which is about App Review of pages_messaging_phone_number. You can pass review and still hit 2018021 for the fee, or the reverse. Normal sends to PSIDs on the same Page are unaffected.

What it looks like

{
  "error": {
    "message": "(#200) Requires phone matching access fee to be paid by this page unless the recipient user is an admin, developer, or tester of the app.",
    "type": "OAuthException",
    "code": 200,
    "error_subcode": 2018021,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • Sending with recipient.phone_number to someone without a role on the app, before the Page has phone matching access.
  • Testing successfully with app testers, then launching to real customers without arranging access.
  • Moving a phone matching integration to a different Page that lacks the access.
  • Assuming App Review of pages_messaging_phone_number alone unlocks phone matching.

How to fix Messenger error 200

  1. 1Confirm the request uses recipient.phone_number; PSID sends are not affected by this gate.
  2. 2Check whether the Page has phone matching access arranged with Meta, and arrange it if your use case qualifies.
  3. 3Meanwhile, keep testing with people who hold admin, developer or tester roles on the app.
  4. 4Offer a PSID-based alternative, such as an m.me link or a Messenger checkbox, so customers can start the conversation themselves.

How to stop it recurring

Treat phone-number messaging as a gated feature with its own launch checklist: review status, Page access, and a fallback. In most cases the more durable path is letting customers open the thread themselves, for example with a link from the Messenger link generator, which gives you a PSID with none of these gates.

Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.

Related codes

Error 200 - quick answers

What does Messenger error 200 mean?

Code 200 with subcode 2018021 relates to customer matching, the Messenger feature that lets a Page start a conversation by sending to a phone number instead of a Page-scoped ID. The message is self-explanatory: "Requires phone matching access fee to be paid by this page unless the recipient user is an admin, developer, or tester of the app." That sentence describes two separate gates.

How do I fix Messenger error 200?

1. Confirm the request uses recipient.phone_number; PSID sends are not affected by this gate. 2. Check whether the Page has phone matching access arranged with Meta, and arrange it if your use case qualifies. 3. Meanwhile, keep testing with people who hold admin, developer or tester roles on the app. 4. Offer a PSID-based alternative, such as an m.me link or a Messenger checkbox, so customers can start the conversation themselves.

Stop debugging Messenger by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.