​
Overview

The Meta proxy allows you to use Meta’s WhatsApp Cloud API directly through Kapso. All requests are forwarded to Meta while Kapso handles authentication and data synchronization.

​
Authentication

Two options:

​
Option 1: Bearer token

Use the WhatsApp configuration’s access token: 
Authorization: Bearer YOUR_WHATSAPP_ACCESS_TOKEN

​
Option 2: Project API key

Use your Kapso project API key: 
X-API-Key: YOUR_PROJECT_API_KEY
When using X-API-Key authentication, the WhatsApp configuration is determined from the IDs in your request URL:
  • Endpoints with phone_number_id → resolves config by phone number ID
  • Endpoints with business_account_id → resolves config by business account ID
  • Media endpoints with media_id → requires phone_number_id as query parameter
The API key must belong to the same project as the WhatsApp configuration.

​
Base URL

https://app.kapso.ai/api/meta/{graph_version}/{endpoint}
Example: 
https://app.kapso.ai/api/meta/v21.0/123456789/messages

​
Supported endpoints

  • /{phone_number_id}/messages - Send messages
  • /{phone_number_id}/settings - Manage settings
  • /{phone_number_id}/flows - WhatsApp flows
  • /{phone_number_id}/media - Upload media
  • /{phone_number_id}/whatsapp_business_profile - Business profile
  • /{business_account_id}/message_templates - Manage templates
  • /{media_id} - Fetch/delete media

​
Data synchronization

All operations through the proxy create the same data in Kapso as using the native Kapso WhatsApp API:
  • Messages are tracked in conversations
  • Templates are synced
  • Contacts are created/updated
  • Analytics and logs are recorded

​
Meta documentation

For detailed endpoint documentation, see Meta’s WhatsApp Business Platform API.