How to Use Your WhatsApp Business API Account

Your WABAccs account comes with 4 credentials: Business ID, Application ID, Application Key (Secret), and Access Token. This guide walks you through connecting these credentials to a BSP or directly to the WhatsApp Cloud API, then sending your first messages.

Step 1: Understand Your Credentials

When you receive your account, you'll get four key parameters:

1. Business ID — Your WhatsApp Business Account identifier on Meta's platform. Used to manage phone numbers and business settings.
2. Application ID — The Meta App ID associated with your WABA account. Required for API authentication and app-level configuration.
3. Application Key (Secret) — The app secret used to verify API requests and generate access tokens. Keep this secure and never share it publicly.
4. Access Token — A long-lived token (EAA prefix) for authenticating API calls. Use this in the Authorization header of every request: Bearer YOUR_TOKEN.

Step 2: Choose Your Integration Path

You have two options to use your WA API account:

• Option A: BSP Partner — Connect to a Business Solution Provider like 360Dialog, Gupshup, Twilio, or MessageBird. BSPs provide a managed interface with webhook handling, template management, and visual builders. Easiest for non-technical users.
• Option B: Cloud API Direct — Use the Meta WhatsApp Cloud API directly with your credentials. Full control and no BSP fees, but requires your own webhook server and API integration. Best for developers.

Step 3: Connect to a BSP

If using a BSP (recommended for most users):

1. Sign up at your chosen BSP's platform (e.g., 360dialog.com or gupshup.io).
2. Select "Bring your own number" or "Connect existing WABA" during setup.
3. Enter your Business ID and Access Token when prompted.
4. The BSP will verify the connection and activate your account on their platform.

Step 4: Configure Your Webhook

Set up a webhook endpoint to receive incoming messages, delivery receipts, and status updates. If using a BSP, they handle this for you. If using the Cloud API directly, configure the callback URL in your Meta App settings under Webhooks. Your endpoint must respond to GET (verification) and POST (events) requests.

Step 5: Create Message Templates

Before sending business-initiated messages outside the 24-hour customer service window, you need approved message templates. Create templates in your BSP dashboard or via the API. Templates can include text, images, documents, and interactive buttons. Meta typically reviews templates within 24 hours.

Step 6: Send Your First Message

Use the API to send a test message. With the Cloud API, the endpoint is POST /v21.0/{phone_number_id}/messages. For customer-initiated conversations (within the 24-hour window), reply freely. For business-initiated messages, use an approved template. Your account supports up to 1,000 new conversations per day.

Pro Tip: To maximize your 1000 daily conversation limit, prioritize high-value customer segments and use message templates that drive replies. Each replied conversation opens a 24-hour window for free-form messaging.

Common Setup Questions

Do I need a Meta Developer account?

No. The account is already set up with all credentials. You can connect directly to a BSP or use the Cloud API with the provided Access Token. No additional Meta registration needed.

Can I switch BSPs later?

Yes. Your account credentials work with any BSP. You can migrate from one BSP to another. However, some BSP-specific configurations (templates, phone number routing) may need to be recreated on the new platform.

What happens if my Access Token expires?

Long-lived tokens can expire or be revoked. If this happens, you may need to generate a new token through the Meta App Dashboard or contact support. Keep your Application ID and App Secret secure — they're used to generate new tokens.