Count = 0: Your account is very new or you only interact with legacy users. Count = 50: You have interacted with 50 users who have modern WhatsApp accounts with LIDs. Count = 10,000: You run a large-scale bot that has processed thousands of unique users. ---

Get LIDs Count

Returns the number of known LIDs.

GET

https://api.wawp.net/v2/lids/count?access_token=123456789&instance_id=123456789

Authentication Required

Test /v2/lids/count endpoint

Supports

GET

No query parameters required

This endpoint doesn't expect data in the URL.

Stats

Returns the number of LID-based contacts known to the device.

Health

Zero count might indicate LIDs are not enabled for this session.

Best practices

Use this for debugging synchronization issues.
Monitor this count to track migration to the new architecture.

Measuring Your Identity Graph: LID Count

The /v2/lids/count endpoint returns a simple integer: the total number of LID-to-Phone mappings your session has cached.

📊 What This Number Means

This is not the number of contacts you have. It is the number of privacy-aware identities your bot has encountered.

Interpretation

Count = 0: Your account is very new or you only interact with legacy users.
Count = 50: You have interacted with 50 users who have modern WhatsApp accounts with LIDs.
Count = 10,000: You run a large-scale bot that has processed thousands of unique users.

🛠️ Use Cases

1. Pagination Planning

Before calling /v2/lids to fetch the full list, check the count.

If count < 100: Fetch everything in one call.
If count > 10,000: Use aggressive pagination (limit=1000, offset=0...10000).

2. Analytics Dashboard

Display this metric to your operations team.

Metric: "Unique Privacy-Aware Users".
Trend: If this number grows faster than your total contact count, it means more users are adopting WhatsApp's privacy features.

3. Cache Warming

If you are migrating to a new server, you can use this count to estimate how long it will take to rebuild your LID cache.

Request Parameters

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

URL Parameters

Passed in the URL query string

	`string`		Your unique WhatsApp Instance ID Example:
	`string`		Your API Access Token Example:

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/lids/count";
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 === 401) {
23      console.error("Error 401: Unauthorized - Invalid or Missing Access Token");
24    }
25    if (response.status === 500) {
26      console.error("Error 500: Internal Server Error - Unexpected Failure");
27    }
28
29    const errorText = await response.text();
30    console.error(`Error ${response.status}: ${errorText}`);
31  })
32  .catch((error) => console.error("Network Error:", error));

Interactive SamplesUTF-8

Ln 32, 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.

Success

application/json

number *

Example

{
"count": 42
}

Unauthorized - Invalid or Missing Access Token

Internal Server Error - Unexpected Failure