url to your customer. Email it, or put it behind a Connect WhatsApp button in your settings screen.
For the full connect story (console vs platform, webhooks, reconnect), see Connecting WhatsApp.
Options
Who pays Meta
Withcustomer_managed, the default, Meta bills the business for its messages on its own Meta payment method, at Meta’s rates. LazyApp charges nothing per message, and your platform wallet pays only ₹999 a month for the connected number.
Use partner_managed only when LazyApp pays Meta for that account through a LazyApp credit line. Then each paid message is debited from a wallet: Meta’s rate, plus 5% when the WhatsApp account is not billed in USD and a further 5% for messages not sent through LazyApp. See Wallets. Choose deliberately: the mode is fixed for the account once the customer connects. See How platform billing works and Meta message billing.
Starter templates
When a customer connects through a setup link, LazyApp can seed their workspace with a pre-built template set — appointment reminders, order updates and the like. Passtemplate_set when creating the link:
GET /v1/templates/sets. Do not hardcode them — the available sets depend on this installation’s configuration.
Do not trust the redirect
Theredirect_url fires in the customer’s browser. It can be reached without the connection having succeeded, and it will not fire at all if they close the tab after a successful connect.
Treat it as UX only. Confirm from the server side:
customer.connected
The connection is live and ready to send.
setup_link.failed
The attempt failed. Show your customer what to fix and issue a new link.
Revoking
204. The URL stops working immediately. GET /v1/platform/setup-links lists links, page-numbered, with usable telling you whether each still works, so a support agent can see at a glance whether a customer’s link expired.