Pular para o conteúdo
Start free

Wabery documentation

Este conteúdo não está disponível em sua língua ainda.

Build and operate a hosted agent, or integrate WhatsApp Business, Instagram Direct, and Facebook Messenger through one API. Wabery brings project-based client work, website chat, bookings, leads, channel delivery, media, Flow encryption, signed events, hosted functions, and retries into one platform.

You bring the product logic. Wabery carries the conversation.

New here? Start with the Quickstart.

What you get

Section titled “What you get”
Unified channelsUse WhatsApp, website chat, Instagram, and Messenger in one project.
ReservationsManage tables, classes, private appointments, waitlists, and customer passes.
Lead qualificationCollect confirmed enquiries and give the team a clear follow-up queue.
Website chatInstall a branded chat widget on approved websites.
Client project accessShare one project's inbox, bookings, leads, and details without exposing your organization.
Media messagesSend and receive images, documents, audio, and video with one normalized contract.
PHP, Python & API clientsUse the REST API directly or import its OpenAPI contract into your preferred client.
Signed webhooksEvery message, status, and submission delivered as a typed, signed event.
WhatsApp FlowsNative in-chat forms that return clean, validated submissions.
Hosted functionsServer-side TypeScript handlers for workflow and agent tool logic.
Registration intentsSingle-use WhatsApp onboarding links safe to create from your app.
WhatsApp broadcastsSend approved templates to a prepared, consent-eligible audience.
WhatsApp CallingConnect calls to your WebRTC or SIP application with signed signaling webhooks.
CLIManage channels, contacts, broadcasts, Flows, and hosted functions.
WhatsApp MCP ServerHand Wabery to Claude, ChatGPT, Cursor, or Codex and build by describing it.
SDK API referenceGenerated reference for every @wabery/sdk method, type, and helper.

If you just signed up

Section titled “If you just signed up”

Do not start with API keys. First decide whether Wabery or your own backend will write customer replies. Getting started explains both paths, then takes you to the sandbox test.

Come back here when you need the API itself.

Authentication

Section titled “Authentication”

Every REST request uses a project-scoped Bearer API key. Create keys yourself in the dashboard — there is no contact-sales step:

Terminal window
curl https://api.wabery.com/v1/me \
  -H "Authorization: Bearer $WABERY_API_KEY" \
  -H "Wabery-Version: 2026-06-18"

Secret keys are prefixed wab_live_ and must stay on the server. Publishable wab_pub_ keys are only for registration intents. Scopes, rotation, and webhook signing secrets are documented in Authentication.

Endpoints and example request

Section titled “Endpoints and example request”

The canonical REST base URL is https://api.wabery.com/v1. The machine-readable contract is the OpenAPI 3.1 specification. Common first endpoints:

Method Path Use
GET /me Confirm the key, organization, and selected project.
GET /projects List projects the key can access.
GET /channels List sandbox and production channels.
POST /messages Send text or channel-supported rich content through WhatsApp, Instagram, or Messenger.
GET /conversations/{id}/messages Read thread history.

Send a text reply once you have a channel_id and conversation_id from the sandbox conversation:

Terminal window
curl https://api.wabery.com/v1/messages \
  -H "Authorization: Bearer $WABERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel_id": "channel_...",
    "conversation_id": "conversation_...",
    "text": "Thanks for your message"
  }'

Install the official CLI from npm when you want the same API from a terminal: npm i -g @wabery/cli. The hosted MCP server is https://mcp.wabery.com.

Wabery developer resources also include authentication, errors and rate limits, webhooks, the sandbox, WhatsApp Calling, and the deprecation and sunset policy.

Find features in the dashboard

Section titled “Find features in the dashboard”

The left sidebar groups the current project’s work. Some items appear only when that project has the matching module or permission.

Group Sidebar Use it for
Daily work Inbox Read and reply to conversations, including human handoff.
Daily work Bookings Open the calendar, appointment requests, waitlist, customer passes, and booking settings when available.
Daily work Leads Review confirmed enquiries and manage lead settings when enabled.
Daily work Contacts Browse enrolled contacts, consent, language, and suppressions.
Manage Agent Configure, test, and publish the hosted agent, or manage external reply routing.
Manage Channels Connect WhatsApp, website chat, Instagram, or Messenger. Open a WhatsApp channel to reach its Flows, Templates, and Broadcasts tools.
Manage Settings Open Project details, Project access, Alerts, and Technical & deletion according to your role.
Developer Access Manage connections, project API keys, and browser-safe registration.
Developer Webhooks Configure the endpoint and inspect delivery status, retries, and payloads.
Workspace Projects Switch projects, add a project, or copy eligible saved configuration.
Workspace Usage & billing Review recorded usage, plans, wallet settings, and available billing details.

Automations and hosted functions live inside Agent. WhatsApp Flows, Templates, and Broadcasts live with the relevant WhatsApp channel. Organization team and general settings sit in the organization menu at the bottom of the sidebar.

How it fits together

Section titled “How it fits together”
  1. Choose who replies — use a Wabery hosted agent or connect your own backend through webhooks and the send API.
  2. Test in the sandbox — use the shared WhatsApp number before connecting a client channel.
  3. Send & receive — call the API (or SDK) to send messages; receive inbound messages, files, and statuses as signed webhooks, and pull thread history from the conversations API.
  4. Register customers — use registration intents to link a customer’s WhatsApp identity to your own user id without exposing a secret key.
  5. Collect structured data — define a WhatsApp Flow once and get back clean submissions at your endpoint.
  6. Broadcast safely — prepare a frozen, consent-eligible audience, review its counts, then send or schedule an approved WhatsApp template.
  7. Run workflow logic — deploy hosted functions when an automation or agent tool needs server-side TypeScript.
  8. Hosted AI agents — create or change only the Draft. Test it in Sandbox. Publish to Live from Agent after review. External AI, MCP, and config apply cannot edit Live.
  9. Business workflows — turn on Leads independently, or publish booking rules and launch booking actions separately when the project uses Reservations.
  10. Client collaboration — invite a client to one project as View only or Editor without exposing organization billing, credentials, or other clients.

Capability map

Section titled “Capability map”

Wabery’s public API, SDK, CLI, and MCP server cover the full messaging workflow:

Area What you can do
Channels List connected WhatsApp, website chat, Instagram, and Messenger channels, set routing modes, inspect routing warnings, and check WhatsApp publish readiness.
Website chat Configure an allowed-origin website widget and route its conversations through the project.
Reservations Configure and operate tables, classes, or private appointments with waitlists, customer passes, and read-only calendar sharing.
Lead qualification Collect confirmed enquiries, review interest signals, update stages, and notify the responsible team.
Client project access Give a client limited View-only or Editor access to their project workspace.
Messages Send text and channel-supported media, plus WhatsApp templates, interactions, reactions, locations, stickers, Flows, Calling prompts, commerce, and eligible regional payment messages. Track delivery with message.status webhooks.
WhatsApp Groups Manage eligible Cloud API WhatsApp groups, join requests, participants, group sends, commerce restrictions, attribution, and group-aware status webhooks.
WhatsApp management Manage business profiles, commerce, QR codes, media lifecycle, registration, webhook subscriptions, calling, funding diagnostics, blocking, and Meta account data without exposing Meta credentials.
Inbound events Receive signed message.received webhooks for text, media files, locations, contacts, unsupported Cloud API envelopes, and other inbound message types. Media files include short-lived Wabery download URLs.
Conversations List conversations and message history; retained inbound media is re-signed when read through the conversation history API.
Contacts & registration Enroll opted-in contacts server-side, or mint browser-safe registration intents that link a customer’s WhatsApp identity to your own user id.
Broadcasts Import or select consented contacts, freeze an audience snapshot, then send or schedule approved localized WhatsApp templates with frequency limits, suppressions, and delivery counts.
WhatsApp Flows Author static or dynamic Flows, publish them to Meta, localize by config key, run data-exchange endpoints, inspect dispatches, submissions, and flow event logs.
Hosted functions Deploy project-scoped TypeScript handlers, test them, expose them as Business Agent or MCP-callable tools, and inspect invocation logs.
Templates Create, submit, inspect, and send WhatsApp templates, including flow-type templates for proactive Flow entry points.
Automations Handle conversations with no code: trigger on welcome, keyword, or any message, then chain actions — send replies, send flows, run a function inline, delay, wait for a reply, branch on a condition, or hand off to a human. Switch to external routing when your webhook owns the reply logic.
Config as code Export, validate, diff, and apply project configuration for webhooks, flows, and automations.
Business Agents Use the REST/OpenAPI surface to provision Meta Business Agents, connectors, tools, thread control, tests, evals, and skills where available for your Meta setup.
Start building — free