WhatsApp inside your own product
Your customers connect their own number through a hosted page that carries your name, keep ownership and Meta billing of their account, and you send, receive and automate for every tenant through one API with signed webhooks.
One API call to onboard ✦ Their account, their Meta bill ✦ No markup on Meta's rates
Your webhook
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo Hotels
Meta's onboarding is the hard part. We host it.
Embedded Signup, phone registration, two-step PINs, webhook subscriptions and every recovery path for a forgotten PIN or a number already in use, packaged behind one API call. You mint a link with your tenant reference and a return URL. Your customer opens a neutral page that shows your name, signs in with Facebook and picks the number. Lodgestory registers it, connects it as a channel and sends them back to you with the channel id.
- Links live 15 minutes to 30 days, seven by default.
- Three completion signals: browser redirect, a poll endpoint and the channel.connected webhook.
- Their WABA, their payment method, billed by Meta directly.
Built for the platform that onboards hundreds of businesses
Onboard with one call
A link per tenant, a redirect, a connected channel. No Meta console, no support tickets, no dead ends on PIN recovery.
Send as any tenant
One API, per-tenant keys exchanged for bearer tokens, every message, template, contact and ticket operation scoped to that tenant.
Hear everything back
Forty signed event types to your endpoints with retries, a 30-day log and replay. Messages, statuses, templates, tickets, calls, AI requests.
Give them Kaylee and MCP
Bot journeys, the AI agent with approvals and an MCP server your tenants' own assistants can use, all already built.
Keys per tenant, tokens that expire, scope that is explicit
Each tenant gets an API key and secret in Developer Access. Exchange them for a bearer token that lives about eight days and send on every request. The public API is deliberately limited to partner-safe operations: contacts, messages, templates, broadcasts, tickets, segments, reports and voice. A suspended organisation answers 423 Locked with a reason and a support link rather than a mystery.
- Service accounts are the identity your automations and the API send as.
- Interactive Swagger at api.lodgestory.com/api/docs/public.
- Templates by API, including carousel and limited-time-offer shapes, with quality synced by webhook.
Replies, statuses and approvals, delivered and signed
One envelope for every event, versioned, with HMAC-SHA256 on each delivery. At-least-once with up to six attempts and a ten-second timeout, per-endpoint event selection and custom headers, automatic pause of a failing endpoint, and a 30-day log you can replay from. For tenants who want an assistant instead of a dashboard, the MCP server runs the same operations with their own sign-in.
- Idempotent by id, no ordering guarantee, snapshots not live reads.
- Chat ids explained once: thread id on messages, conversation id on tickets, states and calls.
- Push for your app through your own APNs and FCM credentials, to the same contact.
Deliveries
Solutions for every team on your side
Your brand on the onboarding page
A neutral page that shows your name, not ours, and sends the customer back to your URL.
Features you did not have to build
Templates, campaigns, bot journeys, Kaylee, tickets and calls, available per tenant the day they connect.
Instagram and Messenger too
The same inbox and API cover Instagram Direct, comment threads and Messenger when your tenants want them.
Push for your app
A push channel through your own credentials, recorded on the same contact as WhatsApp.
One call, one redirect
Mint the link, read the channel id on return, subscribe to channel.connected. Done.
Tokens, not shared secrets
Per-tenant keys exchanged for short-lived bearer tokens; 423 Locked tells you exactly why a tenant is paused.
Signed, retried, replayable
HMAC-SHA256, six attempts, 30 endpoints, custom headers, a 30-day log.
Reference you can run
Interactive Swagger for the public API, and verified code samples on every channel page.
You are not the biller
Each tenant's WhatsApp Business Account is theirs, with their own payment method and Meta's rates, no markup.
Faster time to value
WhatsApp becomes a feature of your product in a release, not a quarter.
Compliance you can point to
SOC 2 Type II aligned controls, GDPR, encryption in transit and at rest, in-region residency.
Reports per tenant
Chats, messages, tickets and campaigns exported per organisation through the Reports API.
In practice
A booking engine ships WhatsApp in one release
A booking engine adds a Connect WhatsApp button to its settings page. Clicking it calls the Lodgestory API with the property's reference and gets back a hosted link. The property owner signs in with Facebook, picks their number and enters the PIN. Minutes later the engine receives channel.connected, starts sending booking confirmations as that property, and routes guest replies into its own interface through webhooks. The property keeps its account and its Meta bill.
Enterprise-grade by default
Per-tenant keys and tokens, signed deliveries, data scoped to each organisation and kept in the region you choose, encrypted in transit and at rest.
Visit the trust centerReading for the integration
Mint the link, handle the return, subscribe to channel.connected.
Everything a partner needs to send as any tenant.
Forty events, one shape, verified in five lines.
Ready to put WhatsApp in your product?
Get a partner key, mint your first onboarding link and connect a test number today.
Questions, answered
The things platform teams ask before they integrate.
A way for a platform, a booking engine, a property-management system or a vertical CRM, to give each of its customers their own WhatsApp number without leaving the product. Your backend mints a one-time hosted onboarding link, your customer signs in with Facebook and picks the number, and it lands as a connected channel reporting your tenant reference. From then on you send, receive and automate for that tenant through the Lodgestory API.
Your customer. They add their own payment method during signup and Meta bills them directly for conversations. Lodgestory never rebills or marks up Meta's charges, so you are not the biller.
Meta's Embedded Signup, phone registration, two-step PINs, webhook subscriptions and the recovery paths for a forgotten PIN or a number already in use are packaged behind one API call and a redirect. The hosted page shows your name, guides PIN entry and SMS or voice re-verification, and reports completion by browser redirect, a poll endpoint and the channel.connected webhook.
With an API key and secret issued per tenant in Settings under Developer Access, exchanged for a bearer token that lives about eight days. The public API is limited to partner-safe operations, and a suspended organisation answers 423 Locked with a reason and a support link.
Through signed webhooks: one envelope for 40 event types, HMAC-SHA256 on every delivery, up to six attempts, up to 30 endpoints per organisation and a 30-day log with replay. Messages carry the channel-level thread id; tickets, chat states and calls carry the conversation id.
Yes. The Lodgestory MCP server lets Claude, ChatGPT or any MCP-compatible assistant read and act in a workspace, scoped to one organisation and the user's role, with the user's own sign-in and no keys shared.
Templates are created and updated through the partner API, including carousel and limited-time-offer shapes and header media uploads, with quality ratings synced by webhook. If you also publish an app, a push channel sends through your own APNs and FCM credentials to the same contact you message on WhatsApp.
Each tenant's channel reports delivery and read statuses by webhook, campaigns track per-recipient attempts, and the Reports API exports chats, messages and tickets per organisation as CSV.