Messenger error 2: Privacy ToS not accepted for custom labels
Last verified against Meta for Developers - Messenger Platform error codes
Privacy ToS not accepted - To use the inbox label API, you need to accept the privacy ToS. Click the link to accept.What error 2 means
Code 2 normally means a temporary service problem, and the top-level text on this one can even read "Service temporarily unavailable." With subcode 2018344, though, nothing is down. Meta's error-codes table explains: "Privacy ToS not accepted - To use the inbox label API, you need to accept the privacy ToS." The real error string includes a link to a terms page for the specific Page, and the table's fix is that "the Page admin must accept the Privacy Terms of Service for Custom Labels."
The Custom Labels API lets an app create labels such as VIP and attach them to Page-scoped IDs so they show up in the Page inbox. Meta gates it behind a one-time terms acceptance that has to be done by a person with admin access to the Page, in the Facebook interface. Your token, your permissions and your request shape can all be correct and the call will still fail until that click happens.
Because the code is 2, generic retry logic will happily back off and try again forever. That never resolves this case; only the Page admin can.
What it looks like
{
"error": {
"message": "(#2) Privacy ToS not accepted - To use the inbox label API, you need to accept the privacy ToS. Click the link to accept.",
"type": "OAuthException",
"code": 2,
"error_subcode": 2018344,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- The Page admin has never accepted the Page contact / custom labels terms for this Page.
- A newly connected Page: terms acceptance is per Page, so a bot onboarded to a second Page hits the error again.
- Retry logic that treats every code 2 as transient and keeps calling the label endpoints.
- The person who connected the Page lacks admin rights, so nobody on the integration side can accept the terms.
How to fix Messenger error 2
- 1Read error_subcode before applying code-2 retry logic, and stop retrying when it is 2018344.
- 2Extract the acceptance link from the returned message and show it to a Page admin in your onboarding UI.
- 3Have an admin of that exact Page open the link while logged in and accept the terms.
- 4Repeat a single label call such as creating a test label to confirm the gate is cleared.
- 5Confirm the call uses Graph API v12.0 or later, the minimum version the custom labels guide lists.
How to stop it recurring
Make labels an opt-in feature in your Page setup flow: when a Page is connected, probe the labels endpoint once and, if 2018344 comes back, put the terms link in front of the admin before any automation depends on labels. Never let tagging failures block the conversation itself; a missing label is cosmetic, a missing reply is not.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
- 2: Unexpected error - retry laterAn unexpected error has occurred. Please retry your request later.
- 10: Application does not have permission for this actionApplication does not have permission for this action
- 200: pages_messaging not reviewed - app not livePermission Error: Cannot message users who are not admins, developers or…
Error 2 - quick answers
What does Messenger error 2 mean?
Code 2 normally means a temporary service problem, and the top-level text on this one can even read "Service temporarily unavailable." With subcode 2018344, though, nothing is down.
How do I fix Messenger error 2?
1. Read error_subcode before applying code-2 retry logic, and stop retrying when it is 2018344. 2. Extract the acceptance link from the returned message and show it to a Page admin in your onboarding UI. 3. Have an admin of that exact Page open the link while logged in and accept the terms. 4. Repeat a single label call such as creating a test label to confirm the gate is cleared. 5. Confirm the call uses Graph API v12.0 or later, the minimum version the custom labels guide…
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.