Skip to Content
TurbineWhats.app
TurbineWhats.app
API schemaPricingWorkspaceOverview

Documentation

Connect an authorized WhatsApp number to your application. Start with a scoped key, then follow the request through the queue and signed delivery events.

Start an integration

Verify your account, connect your number from WhatsApp Linked devices, and create an API key. The trial supports individual text messages to your linked number or support-approved recipients. Group and advanced operations require a paid plan.

Follow the quickstart →

Build against the contract

Use the OpenAPI specification for request schemas, methods and permissions. Sending endpoints return HTTP 202 when a request enters the queue. Read and delivery receipts depend on WhatsApp and the recipient’s settings.

Integration guides

Quickstart

Verify your account, connect a number, create a scoped key, and queue your first text message.

Authentication

Use expiring Bearer tokens with read, send, and manage permissions. Session scoping limits access further.

WhatsApp sessions

Create a session, authorize it through Linked devices, inspect connection state, and manage its lifecycle.

Text messages

Queue a text message using a connected session and a per-message idempotency key.

Images and PDFs

Send JPEG/PNG images and PDF documents as bounded base64 payloads on a paid plan.

Contacts, chats, and groups

Read data available through a connected WhatsApp account using a session-scoped read key.

Delivery and retries

Understand queue acceptance, delivery receipts, and how to handle sends whose outcome is uncertain.

Webhooks

Configure HTTPS destinations, verify raw-body signatures, and deduplicate repeated deliveries.

Limits and billing

Trial restrictions, per-plan sending allowances, time windows, and cancellation behavior.

Errors and troubleshooting

Interpret error codes and choose the appropriate correction rather than repeating requests blindly.

Security and service model

Credential handling, account isolation, data retention, and the limitations of independent WhatsApp connectivity.

API reference

The supported public endpoints, required scopes, response envelope, and format conventions.

Groups

Create groups, manage participants, share invite links, and send messages to a group you are authorized to use.

Capabilities and limits

Supported feature families, engine-dependent behavior, and differences from WHAPI.

Agents and discovery

Public Markdown, OpenAPI and safe access for LLM-assisted integrations.

Group operations

Exact methods, permissions, request bodies and query fields for group operations.

Message operations

Exact methods, permissions, request bodies and query fields for message operations.

Chat operations

Exact methods, permissions, request bodies and query fields for chat operations.

Contact operations

Exact methods, permissions, request bodies and query fields for contact operations.

Presence operations

Exact methods, permissions, request bodies and query fields for presence operations.

Profile operations

Exact methods, permissions, request bodies and query fields for profile operations.

Label operations

Exact methods, permissions, request bodies and query fields for label operations.

WhatsApp channel operations

Exact methods, permissions, request bodies and query fields for whatsapp channel operations.

Status operations

Exact methods, permissions, request bodies and query fields for status operations.

Business catalog operations

Exact methods, permissions, request bodies and query fields for business catalog operations.

Call operations

Exact methods, permissions, request bodies and query fields for call operations.

Connection requirements

This independent WhatsApp Web connection is not an official WhatsApp or Meta API. Relinking and account restrictions can interrupt access. Use consent-based messaging and keep another channel for critical communications.

Agent indexPublic summaryOpenAPICapabilities and limits

Quickstart

Next Page