For when the interface is not where the work happens
Your ERP knows when an invoice is raised. Your booking system knows when an appointment moves. Rather than asking a human to relay that to WhatsApp, have the system send it. This API is deliberately small — it does the few things worth doing programmatically, and does them predictably.
Scoped keys, not a master password
Create as many API keys as you need and give each one only the scopes it requires — messaging, contacts or phonebooks. A key used by your website form does not need permission to read your customer list. Every call is logged against the key that made it, so you can see what your own systems are doing.
- Separate scopes for WhatsApp, contacts and phonebooks
- Multiple keys, revocable individually
- Usage logs per key
- Requests are rate limited, so one runaway script cannot flood your number
What you can call
Send a plain text or media message, send an approved template, list your templates, create and read contacts, and manage phonebooks. Requests and responses are plain JSON over HTTPS — you can drive it from cURL, from PHP, or from whatever your systems already speak.
- POST /send-message — text, image, video or document
- POST /send_template — an approved template with its variables
- GET /templates — the templates available to send
- GET and POST /contacts — read and create contacts with custom fields
- GET and POST /phonebooks — manage the groups campaigns send to
- GET /phone-numbers — the WhatsApp number connected to your account
API messages behave like every other message
Anything you send through the API is written into that customer's conversation in the shared inbox, labelled as API. Your agents see it, your AI reads it as context, and the 24-hour window and template rules apply exactly as they do everywhere else. There is no separate, invisible channel.
- Messages appear in the inbox thread, badged API
- The same window and template rules apply
- Delivery status flows back the same way
- Your AI agent reads API messages as conversation history
The developer API is part of the Growth and Pro plans. Starter includes everything else — inbox, AI, automations and campaigns — but not programmatic access.
See plansFrequently asked
https://api.aptoair.com/api/v1