OpenAPI 3.1 description
A machine-readable contract for listing approved templates and sending a Meta-approved WhatsApp template from an Attio workflow.
Open openapi.jsonDEVELOPERS AND AGENTS
The public WhatSync interfaces, in one place.
Use the workflow API to send an approved WhatsApp template through Meta. Use the agent resources to understand the product and find the right documentation. These are separate interfaces with separate authentication and capabilities.
Workflow API guide
The human guide to connection IDs, service API keys, template approval, request fields, media headers, and JSON responses.
Read the sending guideAgent discovery
A compact llms.txt index tells assistants what WhatSync is for, what it can search, and which public pages answer each question.
Open llms.txtWorkflow API authentication
Every workflow request needs the connection ID in the query string and that workspace's service API key in thex-service-api-keyheader or as a Bearer token. Never put a real key in a prompt, client-side bundle, public repository, or support message.
The WhatsApp MCP product guide describes read-only search over synced message text. Its connector is not the workflow REST API. A client should verify that the MCP hostname supplied for an account resolves before treating setup as complete.