Skip to main content
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?.
  • 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

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)? for the WABA side, or Meta Developer Account Setup for the click-by-click walkthrough that creates both.

​
Frequently asked

No — registering as a developer and creating Apps is free.
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.
It’s technically possible, but keeping one App per business/integration is simpler to manage and troubleshoot — that’s the recommended default.
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.

​
Gotchas & common mistakes

  • 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.