Get General Presence

Get the current presence status (online/offline) for the authenticated session.

GET
https://api.wawp.net/v2/presence?access_token=123456789&instance_id=123456789

Authentication Required

Login to swap the placeholders with your real Instance ID and Access Token.

Log In
Test /v2/presence/all endpoint
GET
GET

No query parameters required

This endpoint doesn't expect data in the URL.

Mirror, Mirror: Checking Your Own Reflection

The /v2/presence (GET) endpoint allows you to programmatically verify how your WhatsApp session appears to the outside world. While you can set your status using the POST method, this GET method is crucial for auditing and synchronization.


🏗️ State Verification

Why check your own status?

1. Audit Loops

If you manage a fleet of 50 support bots, you need a dashboard to see which ones are currently "Online" and accepting chats.

  • Workflow: Central Monitor calls /v2/presence on each instance every minute.
  • Alert: If a bot is supposed to be Online but returns offline, tips: [ { "type": "positive", "title": "User Experience", "content": "Show "typing..." status to make the bot feel more human-like." }, { "type": "info", "title": "Status", "content": "Online status updates can trigger automation flows." } ], recommendations: [ "Do not keep "typing" status active for too long without sending a message.", "Respect user privacy regarding online presence.", "Use presence webhooks to trigger immediate responses." ],

trigger a slack alert to the engineering team. The session might have crashed or been manually toggled by a human using the mobile app.

2. UI Synchronization

If you are building a custom CRM with a "Go Online" toggle button:

  • Problem: You don't know the initial state of the button when the page loads.
  • Solution: Call this endpoint on page load. If it returns available, render the toggle as green (Active). If unavailable, render it as grey (Inactive).

3. Debugging "Ghost" Issues

Sometimes users complain: "I see you online but you aren't replying!"

  • Debugger: Call this endpoint. content:
    • Result: offline.
    • Conclusion: The user is seeing a cached state on their device, or you have privacy settings hiding your real status. The API confirms you are effectively invisible.

🔄 The Feedback Loop

The "Auto-Correction" Pattern

WhatsApp sessions can sometimes drift. For example, if the physical phone loses internet connection for 10 minutes, WhatsApp might automatically mark the session as unavailable.

  • Script:
    1. Cron job runs every 5 minutes.
    2. Step A: Call GET /v2/presence.
    3. Step B: If result is offline AND expected state is online -> Call POST /v2/presence to force it back.
    4. Result: Self-healing availability.

⚠️ Limitations

  • Internal State Only: This endpoint only returns what the WhatsApp Web protocol thinks your status is. It does not strictly guarantee that your phone is reachable (e.g., if the battery died 30 seconds ago, the server might still think you are online for another minute).
  • Privacy Masks: If your privacy settings are set to "Nobody", this endpoint might still return available (because you know you are online), but external users will see nothing. Usage of this data must be combined with an understanding of your privacy configuration.

Request Parameters

Configure the parameters required to interact with this endpoint. All query and body arguments are listed below with their details.

Query Parameters & Request Body

Supported in URL Query String or JSON Body
string

Your unique WhatsApp Instance ID

Example:
string

Your API Access Token

Example:

Build with AI using Wawp MCP

MCP READY

Connect Wawp API directly to Cursor, Windsurf, or Claude Desktop. Let AI write, test, and execute your WhatsApp integration code automatically!

How to Connect

Request Samples

Use these ready-to-go code snippets to integrate our API into your project quickly and efficiently. Choose your preferred language and library.

1const baseUrl = "https://api.wawp.net";
2const endpoint = "/v2/presence";
3const params = new URLSearchParams({
4 "instance_id": "123456789",
5 "access_token": "123456789"
6}).toString();
7
8
9fetch(`${baseUrl}${endpoint}${params ? '?' + params : ''}`, {
10 method: "GET",
11 headers: { "Content-Type": "application/json" },
12
13})
14 .then(async (response) => {
15 if (response.ok) {
16 const data = await response.json();
17 console.log("Success:", data);
18 return data;
19 }
20
21 // Error Handling
22 if (response.status === 400) {
23 console.error("Error 400: Bad Request - Missing Required Parameter(s)");
24 }
25 if (response.status === 400) {
26 console.error("Error 400: Bad Request (XML Format)");
27 }
28 if (response.status === 400) {
29 console.error("Error 400: Bad Request (Plain Text)");
30 }
31 if (response.status === 401) {
32 console.error("Error 401: Unauthorized - Invalid or Missing Access Token");
33 }
34 if (response.status === 401) {
35 console.error("Error 401: Unauthorized (XML Format)");
36 }
37 if (response.status === 404) {
38 console.error("Error 404: Not Found - Session Does Not Exist");
39 }
40 if (response.status === 404) {
41 console.error("Error 404: Not Found (XML Format)");
42 }
43 if (response.status === 500) {
44 console.error("Error 500: Internal Server Error - Unexpected Failure");
45 }
46 if (response.status === 500) {
47 console.error("Error 500: Internal Server Error (HTML)");
48 }
49 if (response.status === 502) {
50 console.error("Error 502: Bad Gateway - Connection Failed to Upstream");
51 }
52 if (response.status === 502) {
53 console.error("Error 502: Bad Gateway (XML Format)");
54 }
55
56 const errorText = await response.text();
57 console.error(`Error ${response.status}: ${errorText}`);
58 })
59 .catch((error) => console.error("Network Error:", error));
Interactive Samples
Ln 59, Col 1javascript

Expected Responses

Explore all possible responses and outcomes from the server. We have documented each status code with data examples to make success and error handling easier.

Presence status retrieved
Type:
Scenario:
application/json
string *

Example

{
"presence": "online"
}
Bad Request - Missing Required Parameter(s)
Unauthorized - Invalid or Missing Access Token
Not Found - Session Does Not Exist
Internal Server Error - Unexpected Failure
Bad Gateway - Connection Failed to Upstream
Previous TopicGet the presence for the chat id
Next TopicSubscribe to Presence

Command Palette

Search for a command to run...