Auphere Embed · Getting started
/ v0.1
Overview
Auphere Embed lets your SaaS platform offer WhatsApp agents and template broadcasts to your own clients — without handling WhatsApp credentials or rebuilding messaging infrastructure.
Auphere Embed is a JavaScript SDK (@auphere/embed) that you install in your web application. It adds two capabilities for each of your clients, directly inside your product:
- Connect WhatsApp — a self-serve flow where your client links their own WhatsApp Business number to their Auphere agent, powered by Meta Embedded Signup.
- Broadcasts — a campaign modal where your client sends approved WhatsApp templates with dynamic variables to a list of recipients you provide.
Mental model
Every concept in your platform maps to one concept in Auphere. You never handle Auphere internals — you always speak in terms of your own identifiers.
| In your platform | In Auphere |
|---|---|
| Your platform (the partner) | A partner account with a secret API key (ak_live_…) |
| A client / business in your product | An isolated workspace, referenced only by your id (external_client_ref) |
| The client's WhatsApp | A WhatsApp Business Cloud API channel owned by that client |
| The client's AI agent | An agent cloned from your partner blueprint at provisioning time |
| Bulk reminders / notifications | A template broadcast to N recipients |
How it works
The SDK is a thin loader. It renders nothing itself beyond a fullscreen iframe overlay served from embed.auphere.com — the same pattern used by Stripe Connect and Plaid Link. This buys you three guarantees:
- No credentials in your bundle. Your page only ever holds a 15-minute session token scoped to a single client. WhatsApp and Auphere credentials never leave our origin.
- Zero-redeploy updates. The modal UI lives on our origin, so we ship fixes and improvements without you touching
package.json. - Isolation by construction. Each client is an isolated workspace. The workspace is selected server-side when the token is minted — a browser can never point a session at someone else’s data.
The integration has exactly two moving parts on your side: a backend endpoint that exchanges your secret API key for short-lived session tokens, and the frontend SDK that mounts the widget with those tokens.
Next steps
- Follow the Quickstart — from API key to a working broadcast button.
- Learn how to provision clients when they sign up in your product.
- Read the security model before going to production.