Wamen documentation

Start with the supported hosted browser module, verify the identity on your backend, then create your application's own session.

Current skateboard release

Wamen is a free experimental service with one unofficial WhatsApp connection and no SLA. The hosted browser module is public. The @wamenjs/auth and @wamenjs/server packages exist in the source tree but are not published on npm yet.

Choose your path

Secure quickstartHosted browser flow, backend verification, and an app-owned cookie session. Hosted scriptScript attributes, link attributes, callback events, and the four-operation browser API. Server verificationExact ES256, issuer, audience, lifetime, identity, and phone claim checks. Security boundariesWhat Wamen proves, what it stores, and what remains the application's responsibility.

The integration boundary

Browser: create state and PKCE, redirect to Wamen, exchange the returned one-time code.
App backend: verify the short-lived identity token and map the pairwise subject to an app user.
App session: issue an opaque Secure, HttpOnly cookie owned by the application.

Wamen proves control of a WhatsApp identity. It is not your user database, authorization layer, or durable session provider.

Using an AI coding agent

Use the prompt in the quickstart. The root llms.txt is a curated index, and llms-full.txt contains the complete current integration contract.

llms.txt is an emerging proposal for inference-time documentation discovery. It does not control AI crawlers, grant training permission, or create a search-ranking signal.