Messenger Platform · error code

Messenger error 2018389: Page Not Allowlisted for calling

ConfigurationPermissions, app review & thread control

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Each Facebook page must be allowlisted by Meta to access the calling alpha

What error 2018389 means

Code 2018389 is the access gate for Messenger calling, the API that lets a Page accept voice calls from people in Messenger through your app. Meta's error-codes table titles it "Page Not Allowlisted" and explains: "Each Facebook page must be allowlisted by Meta to access the calling alpha."

The key word is alpha. Calling on the Messenger Platform is a limited program, and the Page itself has to be enabled by Meta. App permissions, webhooks and code can all be in place, and every call endpoint for that Page will still return this error until Meta adds the Page. Another Page on the same app may work if it is in the program, which is the quickest way to confirm the diagnosis.

The table's suggested solution, "Try again later or reduce the frequency or amount of API calls the app is making," is generic text reused from the rate-limit row of the same table. Throttling does not fix an allowlist problem, so do not let a retry policy loop on this code.

What it looks like

{
  "error": {
    "message": "(#2018389) Each Facebook page must be allowlisted by Meta to access the calling alpha",
    "type": "OAuthException",
    "code": 2018389,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • The Page is not enrolled in Meta's Messenger calling program.
  • Testing calling on a new or different Page from the one that was enrolled.
  • Deploying a calling integration to customer Pages without enrolling each one.
  • Assuming app-level access applies to every Page the app manages.

How to fix Messenger error 2018389

  1. 1Confirm which Page ID the request targets, and whether that Page is enrolled.
  2. 2Request access for the Page through your Meta contact or the calling program's process.
  3. 3Disable the calling feature for Pages without access instead of retrying.
  4. 4After enrollment, subscribe the app to the calls webhook field and test with a real inbound call.

How to stop it recurring

Keep a per-Page feature flag for calling that is set only after Meta confirms access, and have your setup flow check it before exposing call controls. Treat 2018389 as a configuration state, not as an error to retry, and hide call buttons on Pages that lack access so people are not invited to call a Page that cannot answer.

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

Related codes

Error 2018389 - quick answers

What does Messenger error 2018389 mean?

Code 2018389 is the access gate for Messenger calling, the API that lets a Page accept voice calls from people in Messenger through your app. Meta's error-codes table titles it "Page Not Allowlisted" and explains: "Each Facebook page must be allowlisted by Meta to access the calling alpha." The key word is alpha. Calling on the Messenger Platform is a limited program, and the Page itself has to be enabled by Meta.

How do I fix Messenger error 2018389?

1. Confirm which Page ID the request targets, and whether that Page is enrolled. 2. Request access for the Page through your Meta contact or the calling program's process. 3. Disable the calling feature for Pages without access instead of retrying. 4. After enrollment, subscribe the app to the calls webhook field and test with a real inbound call.

Stop debugging Messenger by hand

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