Skip to main content
POST
Join newsletter
Auth: TokenAccount or TokenInstanceRate-limit: Global (100/min) • Idempotent: partial (an already-followed newsletter is usually a silent no-op)

Description

Subscribes (follows) the account to a newsletter. After join, the newsletter shows up on GET /list and incoming messages arrive as message.exchange with chat.type = "newsletter".

Examples

By JID

Subscribes the account by passing the canonical newsletter JID (@newsletter). It’s the most direct format, no need to resolve a link or code first.
Subscribes the account by passing the full invite link (https://whatsapp.com/channel/...). The server extracts the code from the URL suffix and resolves the JID before following.

By code

Subscribes the account by passing only the invite code (link suffix, without the domain). A shortcut for when you’ve already extracted the code.

Success response

The response always returns the canonical newsletter JID in channelJid, even when the input was a link or invite code. Use that value as the identifier in subsequent calls (/info, /leave).
200 OK

Path parameters

string
required
Instance name.

Headers

string
required
TokenAccount or TokenInstance.
string
required
application/json

Request body

string
required
@newsletter JID, full link or invite code.

Notes

  • The response always returns the canonical JID in channelJid, useful when the input was a link / code.
  • After join, the propagation to GET /list can take a few seconds.
  • In rare cases, private newsletters require approval from the owner, join returns success but the newsletter only shows up in list after the approval.
  • Invite links can be revoked by the owner, old codes start failing with newsletter not found.

Errors

Envelope: