> For the complete documentation index, see [llms.txt](https://tutorials.kuasa.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.kuasa.io/getting-started/kuasa-campaigns/whatsapp-official/get-started.md).

# Get Started

<mark style="color:red;">**Note: The flow and interface may vary depending on each Facebook account. If you encounter any difficulties during this process, please contact the support team for further assistance.**</mark>

Before we start, please ensure you have the following:

1. A **SIM card** number that is **not registered with any WhatsApp** account.
2. A **Facebook account** (active and got the password for verification)
3. **Card details** for payment transactions.

To connect your WhatsApp Official to Kuasa, you will need to provide 4 details:

1. **WhatsApp Business ID (WhatsApp Business Account ID)**
2. **App ID**
3. **Number ID (Phone number ID)**
4. **Access Token**

In this tutorial, we will guide you to get all 4 details mentioned above. Let's go!

To get started, you need to register a **Developer & Business App account** with the **META Platform.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tutorials.kuasa.io/getting-started/kuasa-campaigns/whatsapp-official/get-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.