Wapi.go

A Go SDK for the WhatsApp Business (Cloud) API, published by WapiKit (golang.wapikit.com). It wraps the raw HTTP API so a Go backend can do WhatsApp messaging without hand-building request payloads.

What it does

• Inbound: receive incoming messages, delivery/status updates, and notifications (via webhooks).
• Management: administer WhatsApp Business Accounts, message templates, and business phone numbers.
• Multi-number: run several phone numbers at once for two-way messaging.
• Abstraction-first: simplified constructors/methods hide the manual payload construction the underlying Meta API otherwise requires.

Where it sits

Wapi.go is a client-SDK layer over the platform — one of the two ways integrators bridge an application to WhatsApp (the other being a BSP). It is the transport plumbing a chat bot sits on top of; an LLM bot like whatsapp-chatgpt-bot is exactly the kind of consumer such an SDK serves, though that bot uses a different vendor (Wassenger) for connectivity.

Tier

T2 — first-party SDK documentation (authoritative about its own surface), but the intro page is thin on license, maintainer detail, and maturity/governance. Feature claims are the vendor's own.

Re-checked 2026-08-31

The guide is still up and still describes the same four capabilities recorded above — inbound messages and status webhooks, account/template/phone-number management (the current page also names analytics), multi-number operation, and payload abstraction. Two months on it still publishes no version number, no changelog and no licence on the introduction page, which is the reason this page has stayed at T2: the SDK is documented as a capability list rather than as a released artifact, so there is nothing to check a claim against and nothing to date. It does now advertise an llms.txt documentation index, which is the only visible change.