API reference overview
Browse every endpoint, try requests in the playground, and jump to narrative examples.
The API reference tab is generated from the checked-in OpenAPI spec (openapi/openapi.json), synced from https://api.wazapin.com/openapi.json.
Base URL
https://api.wazapin.comAuthentication
Send your API key on every request:
X-Api-Key: YOUR_API_KEYSee Authentication for setup and verification.
How this tab is organized
| Section | Use case | Contents |
|---|---|---|
| Overview | Guide | This page |
| System | Core integration | Health, readiness, version |
| Messages | Core integration | Send and read messages |
| Channels | Core + setup | List channels, inspect status, and complete channel setup |
| Contacts | Core integration | Contact records and phone/profile lookup for messaging |
| Templates | Core + template management | List, sync, create, and submit templates |
| Media | Core integration | Upload and manage sendable media assets |
| Webhooks | Core integration | Customer-facing outbound webhook endpoint management |
| WABA | Setup helper | Official WhatsApp Business onboarding helpers |
| API keys | Core integration | Create and revoke workspace API keys |
| Auth | Account access | Login, me, logout |
| Request guides | Guide | Narrative examples with playground (api: frontmatter) |
Playground
- Open an operation page (for example Send a message).
- Enter your X-Api-Key in the playground auth field.
- Pick an example from the dropdown (text, template, buttons, …) or edit the body.
- Run the request against
https://api.wazapin.com.
If the playground fails behind your proxy, allow POST to /_mintlify/api/request. See API playground.
Message guides vs OpenAPI
Step-by-step message types (limits, examples) live under Sending & receiving. OpenAPI pages document HTTP shape and schemas.