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.com

​
Authentication

Send your API key on every request: 
X-Api-Key: YOUR_API_KEY
See Authentication for setup and verification.

​
How this tab is organized

SectionUse caseContents
OverviewGuideThis page
SystemCore integrationHealth, readiness, version
MessagesCore integrationSend and read messages
ChannelsCore + setupList channels, inspect status, and complete channel setup
ContactsCore integrationContact records and phone/profile lookup for messaging
TemplatesCore + template managementList, sync, create, and submit templates
MediaCore integrationUpload and manage sendable media assets
WebhooksCore integrationCustomer-facing outbound webhook endpoint management
WABASetup helperOfficial WhatsApp Business onboarding helpers
API keysCore integrationCreate and revoke workspace API keys
AuthAccount accessLogin, me, logout
Request guidesGuideNarrative examples with playground (api: frontmatter)
The API reference includes core integration endpoints plus setup and account-management helpers. For most server-side integrations, start with Messages, Channels, Contacts, Templates, Media, Webhooks, and API keys.

​
Playground

  1. Open an operation page (for example Send a message).
  2. Enter your X-Api-Key in the playground auth field.
  3. Pick an example from the dropdown (text, template, buttons, …) or edit the body.
  4. 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.
Start with Send a message for the full type reference and playground examples.