Skip to main content
Many WaGo endpoints accept either a phone number or a WhatsApp JID. Use consistent IDs in production to avoid sending to the wrong chat.

Phone numbers

Use country code and number without +, spaces, or punctuation:
15551234567
For one-to-one chats, WaGo converts the phone to a WhatsApp user JID internally.

WhatsApp JIDs

Common JID suffixes:
SuffixMeaningExample
@s.whatsapp.netNormal user JID[email protected]
@g.usGroup JID[email protected]
@newsletterNewsletter/channel JID120363151889@newsletter

Groups

Group endpoints usually require a group JID. Group JIDs end in @g.us. Use GET /group/list to list groups known to the connected session. Use POST /group/info when you already have a group JID and need metadata.

Messages

Message operations use:
FieldMeaning
id or messageidWhatsApp message ID returned by send response or webhook.
chat or jidChat JID where the message exists.
participantSender JID inside a group message. Needed for some quoted or group operations.
isfromme / isFromMeWhether the target message was sent by the current session.

Calls

Call endpoints use callID or CallID depending on the endpoint. The value comes from call webhooks, /call/make, or /call/status. Use GET /call/status to list tracked calls:
curl -H "token: YOUR_TOKEN" \
  http://localhost:1337/call/status

Labels

Label endpoints use labelid. Existing labels come from WhatsApp state. POST /label/edit can create, update, or delete labels depending on the action value.