> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/meta-business-setup/official-business-accounts-blue-badge.md).

# Official Business Accounts (Blue Badge)

Learn about WhatsApp Official Business Accounts and the blue badge application process.

An Official Business Account (OBA) is Meta's blue-checkmark verification for authentic, well-known brands on WhatsApp — it's a trust badge, not a requirement for using the WhatsApp Business API. This section explains what OBA is and what the blue checkmark actually means, the eligibility criteria your business must meet before applying, how to submit an OBA request (including the separate process required for Coexistence numbers), and what to do if your request is rejected.

#### In this section

* Understanding Official Business Accounts (OBA)
* Eligibility criteria for Official Business Accounts
* How to apply for an Official Business Account (OBA)
* What if your Official Business Account (OBA) request gets rejected?
* How to apply for an Official Business Account (OBA) for a Coexistence number
* Frequently asked questions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/meta-business-setup/official-business-accounts-blue-badge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
