WazzaBeeWhatsApp API
for developers
Send messages and templates from your own product, receive incoming messages through webhooks and manage channels over a clear REST interface. The access key is issued in your dashboard.
- REST and webhooks
- Key in your dashboard
- Documentation with examples
How leads are lost right now
Three situations almost every company knows
Ready-made integrations don't cover your process
You have your own system: billing, a customer portal, an intranet or a mobile app. Off-the-shelf connectors simply don't fit it.
Notifications are sent by hand
Something happens in your product and a person sends the customer a message, late and with mistakes.
Incoming messages go nowhere
The customer replied in the messenger, but the system knows nothing about it: the request is created manually, or not at all.
What a message sent through the API looks like
Your product calls a method, the customer gets a message, and their reply arrives as a webhook.
How do I get started with the WhatsApp API?
From sign-up to your first request: the line goes live in about 15 minutes, and the token is issued right after.
Account and line
You sign up and create a WhatsApp Business API line that the token will be linked to.
Sender number
You fill in the Meta form and verify the number your messages will be sent from.
Token in the API settings
You issue an access key in the dashboard. No applications or approvals.
Webhook URL
You specify your handler, and incoming messages start arriving there.
Templates for moderation
You submit templates to Meta. While they're being reviewed, you can reply to customers with free-form text within the 24-hour window.
What you get
Sending messages
Text, media and approved templates with variables, all in a single request.
Webhooks for incoming messages
Customers' replies hit your endpoint and are handled by your own logic.
Channel management
The list of lines, their state and settings are all available through the API.
Contacts and conversations
Methods for working with contacts and conversation history.
Key in your dashboard
The token is issued right away, with no separate requests or approvals.
An official channel
The WhatsApp Business API under the hood, so template broadcasts are permitted by the rules.
Manual sending vs working through the API
For a product, notifications shouldn't depend on a person sitting at a computer
How much will messages through the API cost?
Factor in the notifications your product sends and replies to incoming messages. Rates depend on the recipient's country.
Your country
Meta rates depend on the recipient country. Below are the final prices per message.
Promos, discounts, invitations: marketing messages
Order status, appointment reminders, payment reminders
Everything an agent writes to a customer while the 24-hour window is open. The first 1,000 per month per number are charged at a reduced price
How much does the WhatsApp API cost?
There's no separate API plan: access is included with the line. You pay for the line and for messages at Meta's rates.
WhatsApp Business API channel
29 900 ₸ / month
or $69 · €62
Messages are billed by Meta: the price depends on the recipient's country and the type of conversation. Marketing messages cost more, while replies sent within 24 hours after the customer writes are almost free for the first 1,000 a month per number and billed at the market rate after that. We quote the current rates when you connect.
Payment by Visa or Mastercard; for companies we issue an invoice.
What's included
- Official WhatsApp Business API channel
- Shared chat for the whole team: browser and phone
- Bitrix24 and amoCRM integrations
- Broadcasts and template notifications
- Open REST API and webhooks
- Free widget for your website
- Auto-replies: greeting and after-hours
- Help with setup and templates
- Voice messages transcribed by AI
- Quick reply templates
The first 7 days are free on any plan. Try it on your own customers and only then decide.
Free manager seats: 3. Each extra seat costs 3 000 ₸ a month.
Pay for six months and get 10% off, pay for a year and get 20% off.
What our API covers
You need an API wherever messaging becomes part of the product: notifications from a customer account, order statuses, transaction confirmations, and customer replies flowing back into the system.
Sending from your own logic
An event in your system triggers an API call: the customer receives a message or a template with values filled in, with no operator involved.
Incoming messages as events
A customer's reply arrives as a webhook at your endpoint. What happens next is up to you: create a request, update a status, hand it to an operator.
Meta's rules are built in
You can message first with a template; free-form text works within 24 hours of the customer's enquiry. The API is designed to make that limit explicit rather than a surprise.
It works alongside the inbox
Even with everything automated, real replies arrive in the shared inbox: operators step in wherever a human is needed.
What people build with the API
- Notifications from a customer account
- Order and delivery statuses
- Confirming transactions and bookings
- Payment reminders
- Two-factor codes and service messages
- Passing incoming messages into your own system
- Syncing contacts
- Collecting feedback
Frequently asked questions
Where do we get the access key?
In your dashboard, in the API settings: the token is issued immediately, with no separate application.
Which methods are available?
Sending messages and templates, working with channels, contacts and conversations, plus webhooks for incoming messages. The full reference with examples is in the documentation.
Can we message a customer first?
Yes, with an approved template. Free-form text is available within 24 hours of the customer's enquiry. That's Meta's rule and it applies to everyone.
Are there any rate limits?
Sending speed is limited by Meta's rules and your number's quality. We smooth out the peaks with a queue so messages aren't lost.
Is the API paid?
There's no separate fee, it's part of running the line. You pay for the line and for messages at Meta's rates.
Can the API and human operators work together?
Yes, that's the usual setup: automation sends notifications while operators handle live replies in the shared inbox.
Documentation and related topics for developers
We'll give you the key and the documentation
We connect the line, issue the token and show you request examples. The first 7 days are free, enough to build a prototype.