Pular para o conteúdo principal

How to connect the official API

Video tutorial covering the full path: from an empty instance to the official API connected, including Meta Business, QR code, payment method, merge with the unofficial instance, and GoHighLevel usage.

Direct link: Watch on YouTube

What you need​

  • An empty Stevo instance (no number connected yet).
  • Access to Meta Business with permission to connect WhatsApp Business.
  • A valid phone number (with country code, e.g. +1, +55).
  • A credit card on file in the BM (required for the official API to work correctly).
  • If you use GHL, follow your Stevo plan’s connection flow for the number.

1. Create and name the instance​

  1. Pick any empty instance in the list.
  2. Click to create / set the name (e.g. “Official API – Cai”).
  3. Open that instance’s dashboard.

2. Connect WhatsApp Business (Meta flow)​

  1. On the instance screen, click Connect WhatsApp Business.
  2. Meta’s official flow opens to link the number to the BSP.
    • This step cannot be skipped: Business connection with the provider is mandatory, same as on other official-API platforms (GHL, etc.).
  3. Click Continue and follow your BM screens (layout may differ, flow is the same).
  4. When you see “Connect an app” / WhatsApp Business app, select it and proceed.
  5. Enter the correct country code and phone number.
  6. A QR code is shown. On your phone, in WhatsApp Business (Meta), confirm the prompt and tap Connect, sharing chats as requested.
  7. After scanning, wait about 45 seconds (sometimes a bit longer) for Meta to finish.
“First client” / branding screen

You may see BSP / first client branding in the flow. That is normal for the official API path.

3. Finish on desktop (timezone & account)​

  1. After the QR step, pick the timezone (e.g. São Paulo / UTC−3).
  2. Confirm; the account links.
  3. Meta may ask for a payment method — you can often click Finish first to process and surface the official API in Stevo, then add the card in the BM.
  4. Wait a few seconds up to ~1 minute for Meta to finish internally.

4. Verify in Stevo (token, WABA, number)​

After processing you should see WABA ID, NUMBER, and token where applicable.

  • Health may still show quality / verification updating — refresh until photo and number match the connected account.
  • When Meta completes, the dashboard shows the correct number and photo.

5. Payment method in Meta Business (required)​

  1. From Health, open the shortcut to your BM in Meta Business.
  2. Go to Settings → WhatsApp accounts → Payment settings (wording may vary slightly in Meta’s UI).
  3. Add a payment method (credit card). Without a card, things can break at critical moments.
  4. Pick currency (e.g. USD) and complete the form.
  5. Make sure the card is default (⋯ menu → set as default if needed).

6. Merge: official + unofficial API (same number)​

Disconnects everything on that number

Preparing merge disconnects what is tied to unofficial and official API in that flow (WhatsApp, GHL, etc.). Plan a short maintenance window.

  1. Connect the number in GHL first if needed (e.g. as “number 2” per your panel).
  2. On the official API side, keep the same phone number aligned with that flow.
  3. With both sides on the same number, use the lightning / merge control in Stevo.
  4. Merge only appears for instances with the same number; pick the pair and enable merge.
  5. After enabling, the UI shows merge active.

7. Auto switch (optional)​

To route traffic to the official API automatically in supported scenarios:

  1. Settings → Manage numbers.
  2. Turn on auto switch for the desired number.
  3. When sending through the right path, the system can switch to the official instance per your rule.

8. Health & messaging tiers (Meta)​

Under Health, over time you’ll see delivered/sent in the last 7 days. Meta raises tier limits (often starting around 250, then 1,000, 2,000, etc.) based on usage and reputation — Meta’s rules, not Stevo’s.

9. Templates (create & approve)​

  1. Under Manage templates, create the template (name, Marketing or other category, header, body with or without variables (e.g. Meta-style numbered placeholders), optional footer, quick reply / URL / phone buttons — up to 10; above that WhatsApp may show a list layout).
  2. Create sends the template to Meta for approval — wait until approved.
  3. Variables: when sending, map first name, phone, custom GHL fields, etc.
GHL script for templates

The video mentions a script to list approved templates in GHL. It is usually in the video description, Stevo tutorials, and the official API beta group when available.

10. Send a template from the system​

  1. Use the script flow (copy/paste in GHL) to list approved templates for the official account.
  2. Pick number and template; you can send, preview, or copy generated code for automations or messages.
  3. If there are variables, fill them before send (e.g. first name).

11. Mass broadcast (official API)​

  1. Choose template and variables.
  2. In mass broadcast, e.g. select a GHL tag to load contacts.
  3. Sending follows Meta’s protocol: about 80 contacts every ~60 seconds (Meta-imposed batching, not a Stevo setting).

Summary​

StepAction
InstanceName an empty instance
MetaConnect WhatsApp Business, QR, timezone
StevoCheck token, WABA, number; refresh page
PaymentCard in BM, currency, default card
MergeSame number both sides → enable merge
GHLConnect number; optional auto switch
TemplatesCreate, Meta approval, script / sends

Questions: Stevo support channel. If this helped, share it with GoHighLevel + Stevo users.

Based on the Stevo video tutorial. UI may change between product versions.