APIs for the WhatsApp messaging platform, enabling businesses to communicate with customers through the world's most popular messaging app.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles WhatsApp the way a machine reads it — 178 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WhatsApp scores 67.4/100 (strong), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile WhatsApp
Each block below is one kind of artifact we hold for WhatsApp. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
WhatsApp Flows API
API for creating structured, interactive forms and multi-step flows within WhatsApp conversations, enabling appointment booking, surveys, lead capture, and other guided experien...
WhatsApp On-Premises API
The self-hosted version of the WhatsApp Business API that allowed businesses to run the API on their own infrastructure. This API was deprecated on October 23, 2025, and all use...
WhatsApp Analytics API
Retrieve conversation and template analytics
WhatsApp Assets API
Upload and retrieve flow JSON assets
WhatsApp Assigned Users API
Manage user access to a WABA
WhatsApp Business Accounts API
Manage WhatsApp Business Account information
WhatsApp Business Profile API
Get and update WhatsApp Business profile information
WhatsApp Lifecycle API
Publish and deprecate flows
WhatsApp Media API
Upload, retrieve, and delete media files
WhatsApp Message Templates API
Create, update, and delete message templates
WhatsApp Messages API
Send messages of all types to WhatsApp users
WhatsApp Phone Numbers API
List and manage phone numbers on a WABA
WhatsApp Product Catalogs API
Connect and manage product catalogs
WhatsApp QR Codes API
Create and manage QR codes for customer conversations
WhatsApp Registration API
Register and deregister phone numbers
WhatsApp Subscribed Apps API
Manage webhook subscriptions for a WABA
WhatsApp Two-Step Verification API
Manage two-step verification PIN
Scroll within the panel for all 17 ·
Postman Collections 3
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
WhatsApp Business Management API
OPEN COLLECTIONWhatsApp Cloud API
OPEN COLLECTIONWhatsApp Flows API
OPEN COLLECTIONArazzo Workflows 14
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
WhatsApp Create and Retrieve QR Code
Create a click-to-chat QR code and read back its deep link and image URLs.
ARAZZOWhatsApp Create Template then Send
Create a new message template and send it once it is available.
ARAZZOWhatsApp Build, Publish, and Send a Flow
Create a flow, upload its JSON, publish it, and send it as an interactive flow message.
ARAZZOWhatsApp Verify and Register Phone Number
Request a verification code, verify it, then register the phone number.
ARAZZOWhatsApp Send Message then React to It
Send a text message and then apply an emoji reaction to that same message.
ARAZZOWhatsApp Check Number then Send Interactive Buttons
Confirm the sending number is verified, then send an interactive reply-button message.
ARAZZOWhatsApp Confirm Profile then Send Location
Read the business profile to confirm the sender, then send a location pin.
ARAZZOWhatsApp Find Approved Template and Send
Look up an approved message template by name and send it to a recipient.
ARAZZOWhatsApp Send Text and Mark Inbound Read
Send a text reply and mark the customer's inbound message as read.
ARAZZOWhatsApp Subscribe App to WABA Webhooks
Confirm the WABA is active, subscribe the app to webhooks, then list subscriptions.
ARAZZOWhatsApp Read and Update Business Profile
Read the current business profile, then apply updates to it.
ARAZZOWhatsApp Find and Update Message Template
Locate a template by name and edit its body, when it is in an editable state.
ARAZZOWhatsApp Upload and Send Document
Upload a document file and send it to a recipient with a display filename.
ARAZZOWhatsApp Upload Media and Send Image Message
Upload an image to WhatsApp servers and send it to a recipient by media ID.
ARAZZOScroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Whatsapp Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Whatsapp Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Cloud API
Send and receive messages, media, and interactive content through Meta-hosted WhatsApp infrastructure.
Message Templates
Pre-approved message templates for proactive customer communication with variable substitution.
Interactive Messages
Buttons, lists, product catalogs, and flows for rich customer engagement.
Media Messaging
Send and receive images, videos, documents, audio, stickers, and location data.
Webhooks
Real-time notifications for incoming messages, delivery status, and account events.
Business Management API
Manage WhatsApp Business accounts, phone numbers, and messaging limits.
Flows
Build interactive multi-step forms and workflows within WhatsApp conversations.
Catalogs and Commerce
Share product catalogs and enable in-chat commerce experiences.
Encryption
End-to-end encryption for all messages and media.
Multi-Agent Support
Route conversations to multiple agents with conversation assignment.
Scroll within the panel for all 10 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
WhatsApp Webhooks
WhatsApp Business Platform webhooks deliver real-time notifications for incoming messages, message status updates, template status changes, account updates, phone number quality...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Whatsapp Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 35
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ConversationAnalytics
JSON SCHEMACreateTemplateRequest
JSON SCHEMACursorPaging
JSON SCHEMAMessageTemplate
JSON SCHEMAPhoneNumber
JSON SCHEMASuccessResponse
JSON SCHEMATemplateAnalytics
JSON SCHEMATemplateButton
JSON SCHEMATemplateComponentDefinition
JSON SCHEMAWhatsAppBusinessAccount
JSON SCHEMAAudioObject
JSON SCHEMAContactObject
JSON SCHEMADocumentObject
JSON SCHEMAInteractiveMessage
JSON SCHEMAListSection
JSON SCHEMALocationMessage
JSON SCHEMAMediaObject
JSON SCHEMAReactionMessage
JSON SCHEMASendMessageRequest
JSON SCHEMASendMessageResponse
JSON SCHEMAStickerObject
JSON SCHEMATemplateComponent
JSON SCHEMATemplateMessage
JSON SCHEMATemplateParameter
JSON SCHEMATextMessage
JSON SCHEMAWhatsApp Flow JSON
JSON SCHEMACreateFlowRequest
JSON SCHEMACursorPaging
JSON SCHEMAFlow
JSON SCHEMAFlowValidationError
JSON SCHEMASuccessResponse
JSON SCHEMAUpdateFlowRequest
JSON SCHEMAWhatsApp Message
JSON SCHEMAWhatsApp Message Template
JSON SCHEMAWhatsApp Webhook Payload
JSON SCHEMAScroll within the panel for all 35 ·
JSON Structure 35
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Whatsapp Business Management Api Cursor Paging Structure
JSON STRUCTUREWhatsapp Business Management Api Phone Number Structure
JSON STRUCTUREWhatsapp Cloud Api Audio Object Structure
JSON STRUCTUREWhatsapp Cloud Api Contact Object Structure
JSON STRUCTUREWhatsapp Cloud Api Document Object Structure
JSON STRUCTUREWhatsapp Cloud Api Interactive Message Structure
JSON STRUCTUREWhatsapp Cloud Api List Section Structure
JSON STRUCTUREWhatsapp Cloud Api Location Message Structure
JSON STRUCTUREWhatsapp Cloud Api Media Object Structure
JSON STRUCTUREWhatsapp Cloud Api Reaction Message Structure
JSON STRUCTUREWhatsapp Cloud Api Send Message Request Structure
JSON STRUCTUREWhatsapp Cloud Api Send Message Response Structure
JSON STRUCTUREWhatsapp Cloud Api Sticker Object Structure
JSON STRUCTUREWhatsapp Cloud Api Template Component Structure
JSON STRUCTUREWhatsapp Cloud Api Template Message Structure
JSON STRUCTUREWhatsapp Cloud Api Template Parameter Structure
JSON STRUCTUREWhatsapp Cloud Api Text Message Structure
JSON STRUCTUREWhatsapp Flow Json Structure
JSON STRUCTUREWhatsapp Flows Api Create Flow Request Structure
JSON STRUCTUREWhatsapp Flows Api Cursor Paging Structure
JSON STRUCTUREWhatsapp Flows Api Flow Structure
JSON STRUCTUREWhatsapp Flows Api Flow Validation Error Structure
JSON STRUCTUREWhatsapp Flows Api Success Response Structure
JSON STRUCTUREWhatsapp Flows Api Update Flow Request Structure
JSON STRUCTUREWhatsapp Message Structure
JSON STRUCTUREWhatsapp Message Template Structure
JSON STRUCTUREWhatsapp Webhook Payload Structure
JSON STRUCTUREScroll within the panel for all 35 ·
Examples 35
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Whatsapp Flow Json Example
EXAMPLEWhatsapp Message Example
EXAMPLEScroll within the panel for all 35 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Customer Support
Provide real-time customer service and support through WhatsApp messaging.
Order Notifications
Send order confirmations, shipping updates, and delivery notifications.
Appointment Reminders
Send appointment reminders and allow rescheduling via interactive messages.
Marketing Campaigns
Send promotional messages using approved templates to opted-in customers.
Two-Factor Authentication
Send OTP codes and verification messages for account security.
Chatbot Integration
Build automated conversational bots for FAQs and self-service workflows.
E-commerce
Share product catalogs, process orders, and send payment reminders.
Healthcare Communication
Send appointment reminders, test results, and health tips to patients.
Scroll within the panel for all 8 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Meta Business Suite
Manage WhatsApp alongside Facebook and Instagram from a unified dashboard.
Salesforce
CRM integration for managing customer conversations and contact history.
Shopify
E-commerce integration for order notifications and customer messaging.
HubSpot
Marketing and sales integration for lead nurturing via WhatsApp.
Zendesk
Help desk integration for ticketed WhatsApp customer support.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
WhatsApp Business Platform
Cloud API and On-Premises API for medium and large businesses at scale.
WhatsApp Business App
Free mobile app for small businesses with basic messaging features.
WhatsApp Flows
Interactive forms and workflows within WhatsApp conversations.
Resources
Every other property we hold for WhatsApp — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 17
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 17 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/whatsapp · machine-readable index on apis.io