Artham
ARTHAM

WhatsApp Business API — Partner Integration Setup

Version 1.0  ·  July 2026

Contents

  1. Overview
  2. What Artham Needs Back
  3. Before You Start — Two Meta Portals
  4. Phone Number ID
  5. Permanent Access Token
  6. Webhook Configuration
  7. Message Template
  8. Completion Checklist

1. Overview

Artham sends order-confirmation messages to end clients over WhatsApp and receives their Approve / Cancel replies to authorise trades. This document lists everything the partner's team must configure on their WhatsApp Business Account (WABA) so that these messages send from the partner's number and the replies reach Artham's servers.

It is intended for the person who administers the partner's Meta Business account and WABA. All configuration in Sections 4–7 happens inside the partner's own Meta account; Artham only receives the two values described in Section 2.

2. What Artham Needs Back

Only two values need to be sent to Artham once setup is complete. Everything else is configured inside the partner's own Meta account.

ValueWhere it comes from
Phone Number IDNumeric ID of the sending number (Section 4). This is not the phone number itself.
Permanent Access TokenSystem-User token generated in Section 5.
Send these two values through a secure channel (e.g. a password-manager share or an encrypted message), not over plain email or chat. The access token grants the ability to send messages from the partner's number — treat it like a password.

3. Before You Start — Two Meta Portals

Setup spans two different Meta websites. This is the most common source of confusion, so keep both open, logged in with an account that has admin rights on the WABA:

4. Phone Number ID

  1. Go to developers.facebook.com → My Apps → open the app the WhatsApp number is connected to.
  2. Left sidebar → WhatsApp → API Setup (may be labelled "Getting Started").
  3. Under the "From" dropdown you'll see Phone number ID — a long number. Copy it. SEND TO ARTHAM
  4. Note the WhatsApp Business Account ID (WABA ID) shown on the same page — you'll need it to confirm the template in Section 7.
Do not use the "Temporary access token" shown on this page. It expires in 24 hours and will break sending the next day. The correct, non-expiring token is generated in Section 5.

5. Permanent Access Token

  1. Go to business.facebook.com → Settings (gear icon) to open Business Settings.
  2. Left sidebar → Users → System Users.
  3. Use an existing System User, or click Add to create one (role: Admin or Employee).
  4. Select the System User → Add Assets → choose WhatsApp Accounts (and/or Apps) → select the WABA → enable Full control / Manage.
    This asset assignment is required — without it the token cannot send messages.
  5. Click Generate token → select the app → tick these two permissions:
  6. Copy the token immediately — Meta displays it only once. SEND TO ARTHAM
System-User tokens do not expire (unlike the temporary token in Section 4), so this is a one-time setup.

6. Webhook Configuration

This is what routes the client's Approve / Cancel button taps back to Artham. If this step is skipped, messages will still send but no reply will ever reach Artham, and every order will stall awaiting approval.

  1. Go to developers.facebook.com → same app → WhatsApp → Configuration.
  2. Under Webhook, click Edit and enter exactly:
Callback URLhttps://api.artham.co/dealer/execution/consent/webhook
Verify Tokenwhatsapp_secret_artham
  1. Click Verify and save. Meta will contact Artham's server and the check should pass immediately.
  2. In Webhook fields, find messages and click Subscribe.
    This subscription is essential — it is what actually forwards incoming replies.
Before changing the callback URL: if this same app currently sends webhooks to a system the partner already uses, redirecting it here will move those notifications to Artham. If the partner needs to keep receiving them, tell Artham before this step — there is an alternative setup (sharing the WABA with Artham's app) that avoids the conflict.

7. Message Template

Message templates do not carry over between WhatsApp Business Accounts, so the order-confirmation template must exist and be Approved on the partner's WABA. Create it exactly as specified below — the field structure must match or sending will fail.

  1. Go to business.facebook.com → WhatsApp Manager → Manage templates (confirm the WABA selected at the top matches the WABA ID from Section 4).
  2. Click Create template and configure:
Nameorder_confirm_auto_schedule
CategoryUtility
LanguageEnglish (US) — en_US  not plain "English" (en)
HeaderType Text, content: Order Consent  (static text, no variable)
BodyEnter this text exactly, with the two variables {{1}} and {{2}}:
Order details:
{{1}}
{{2}}
Please review and respond.
ButtonsType Quick reply. Add two, in this order:
1st button = Approve  ·  2nd button = Cancel.
Button order matters — the first must be the approval action.

Sample values for the variables

Meta's template-creation page asks for a sample value for each variable so the template can be reviewed. Enter these:

{{1}}Client : John Doe | Portfolio BSTE
{{2}}Buy APPL Qty : 10 | BUY GOOGL Qty : 5

These samples are only for the approval preview — at send time Artham fills {{1}} and {{2}} with each client's live order details.

Submit for review and wait until status shows Approved (usually minutes to a day). Let Artham know once approved.

8. Completion Checklist

Questions on any step can be directed back to the Artham team.
Artham · api.artham.co · WhatsApp Business API Integration Setup · July 2026