Wapiworld

Wapiworld developer platform

Build tenant-scoped WhatsApp sender workflows with the REST API, the public npm CLI, or the OAuth-protected Streamable HTTP MCP at https://mcp.wapiworld.com/mcp.

Developer resources

• Developer page
• OpenAPI specification
• Authentication guide
• MCP server card
• Agent Skills index
• AI Catalog
• CLI package
• Public CLI source
• Public Agent Skills source
• Public Claude plugin source

MCP tools

• list_projects — List a bounded page of tenant-scoped Wapiworld projects.
• list_instances — List safe WhatsApp sender summaries without secrets or QR pairing data.
• get_instance — Fetch safe operational details for one WhatsApp sender.
• get_instance_status — Check one sender connection without authentication data.
• get_message_recording_policy — Inspect default recording and retention policy without reading messages.
• list_webhook_subscriptions — List sanitized webhook configuration and delivery health for an OAuth operator.
• send_message — Send one explicitly confirmed WhatsApp text; non-idempotent and never automatically retried.

Authentication

REST API keys use HTTP Basic authentication and are pinned to one project with per-resource scopes. The MCP uses OAuth 2.0 with wapiworld:read and a separate wapiworld:write scope. Begin read-only and request write only for a deliberate send.

Safety boundary

The public MCP never returns recorded message bodies, previews, sender names, contact or chat identifiers, WhatsApp message identifiers, QR pairing data, API keys, instance secrets, proxy credentials, webhook signing secrets, complete webhook URLs, or raw provider errors.

send_message is destructive, open-world, and non-idempotent. Show the exact sender, recipient, and complete text; warn that recording settings may persist the text; obtain explicit confirmation for exactly one send; call once; and never automatically retry an uncertain outcome. Transport acceptance is not proof of delivery or reading.