> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What Is a Meta Developer Account — and What Is an 'App'?

> The difference between a Meta developer account, a Meta 'App' (the credentials container for one integration), and a WABA — and how the three fit together.

A Meta **developer account** and a Meta **App** are two different things created back to back
during setup. It's easy to assume "app" means the whole WhatsApp integration — it doesn't, it's
just one specific piece of it.

## Developer account: your login, registered as a developer

* No separate signup — it's the same personal Facebook account from [What Is
  Meta?](/meta-api/concepts/what-is-meta).
* Registered once as a developer, the first time you visit `developers.facebook.com`.
* Free, and it's what lets that account go on to create Apps.

## App: the credentials container for one integration

An **App** is a container you create inside the developer dashboard for one specific
integration. It holds:

* The App ID and App Secret
* Access tokens and permission grants
* Webhook subscriptions
* Which "use cases" are attached to it (e.g. "Connect with customers through WhatsApp")

One developer account can create many Apps — one per project or business it's building for.

## How App, WABA, and Portfolio fit together

| Container          | What it holds                                               | Created                                              |
| ------------------ | ----------------------------------------------------------- | ---------------------------------------------------- |
| Business Portfolio | The business itself — WABAs, Apps, ad accounts, team access | Once per business                                    |
| App                | API credentials and permissions for one integration         | Once per integration, attached to a portfolio        |
| WABA               | Phone numbers, templates, message history                   | Created during App setup, lives inside the portfolio |

The App is the *technical* container — credentials and code-facing settings. The WABA is the
*messaging* container — what actually sends and receives WhatsApp messages. They're linked
together during setup but are not the same object; see [What Is a WABA (WhatsApp Business
Account)?](/meta-api/concepts/whatsapp-api-glossary)
for the WABA side, or [Meta Developer Account
Setup](/meta-api/concepts/meta-developer-account-setup) for the click-by-click walkthrough that
creates both.

## Frequently asked

<AccordionGroup>
  <Accordion title="Do I need to pay to become a Meta developer?">
    No — registering as a developer and creating Apps is free.
  </Accordion>

  <Accordion title="Is my App the same as my Business Portfolio?">
    No. The App is the technical credentials container for one integration; the Business
    Portfolio is the business-level container that owns the App, the WABA, and everything else.
  </Accordion>

  <Accordion title="Can one App connect to multiple WABAs?">
    It's technically possible, but keeping one App per business/integration is simpler to manage
    and troubleshoot — that's the recommended default.
  </Accordion>

  <Accordion title="I already have an App for something else, like Facebook Login. Can I reuse it?">
    You can add the WhatsApp use case to an existing App, or create a new one dedicated to
    WhatsApp. A dedicated App is usually cleaner, since it keeps WhatsApp's credentials and
    webhook config separate from unrelated integrations.
  </Accordion>
</AccordionGroup>

## Gotchas & common mistakes

<Warning>
  * **App ID / App Secret ≠ Phone Number ID / WABA ID.** The first pair authenticates the App
    itself (used in OAuth-style flows); the second pair identifies WhatsApp resources used in
    messaging calls. Mixing these up is a common source of confused API errors.
  * **"App" in casual conversation often means the whole integration** — but on Meta's own
    screens, "App" refers specifically to this credentials container, not the WABA or the
    Business Portfolio.
</Warning>