wa-gateway

gateway · checkingMeta API · checking

Meta API access restricted

Connect WhatsApp

Connect one business number to each workspace. Credentials stay encrypted inside the gateway.

Product

Workspace name

Workspace ID

Dwadie catalogue

Add the real products buyers can order. Prices are Ghana cedis; stock prevents sold-out products appearing.

Product ID

Product name

Price (GH₵)

Stock

Dwadie shop activation

Publish the operating details buyers rely on, review every readiness check, then activate the shop.

Business name

Public phone

Public email (optional)

Public address

Monday opens

Monday closes

Zone ID

Zone name

Fulfilment

Delivery fee (GH₵)

Minimum order (GH₵)

Lead time (minutes)

Payment method

Policy version

Dwadie orders

Financial status and merchant fulfilment remain separate. Refresh after a stale action.

Fulfilment state

Send a message

Goes out through the Cloud API from a number your key is bound to, and lands in the ledger with its delivery meter running.

From number

To (wa_id, e.g. 4917…)

Type

Message

Template (approved only are sendable)

Variable values (comma-separated, one per {{n}})

Products

Choose a product to see its number, inbound route, recent traffic, failures and working surface together.

Ledger

Every message through the exchange, both directions. The meter fills as Meta confirms: accepted, sent, delivered, read.

all apps refreshes every 10 s

Page 1

	app	peer	message	delivery	when

Nothing in the ledger yet. Send a message and it lands here with its meter running.

Apps & numbers

Each app holds its own key and sends only from numbers bound to it. A new key is shown once — store it in the app's env, never here.

App keys and phone-number routing

Apps

app id (slug)

name

Numbers

phone number id

bound app

display

forward inbound to (URL)

Message-template configuration

Templates

Business-initiated messages need one of these, approved by Meta. Approval is asynchronous — refresh to poll.