KK-DATA avatar KK-DATA

Full Process Guide for Exporting WSID of Valid WhatsApp Numbers: From Detection to Field Explanation and API Integration

wa有效号码 wsid kkdata

Complete Guide to Exporting WSID for Valid WA Numbers: From Detection to Field Descriptions and API Integration

In the process of overseas customer acquisition, validating WhatsApp numbers and accurately identifying them is key to improving reach rates. After many teams complete WA valid number detection, they find an important field in the exported data besides phone numbers: WSID (WhatsApp ID). What exactly is this ID? How do you export it? How can you integrate it with an API for batch use? This guide will explain everything clearly.

If you haven’t used a number screening platform yet, you can log in to the KK-DATA Application Console and follow along. If you want to review the documentation first, check out the User Documentation.


What is WSID? Why is Exporting WSID for Valid WA Numbers Important?

WSID is the internal unique identifier assigned by WhatsApp to each account, similar to a user’s “digital ID.” When a person changes their phone number (e.g., swaps SIM cards or changes carriers), WhatsApp often still retains the original WSID as long as they log into the same account. Therefore, WSID is more stable than phone numbers and can track the same user over the long term.

Differences Between WSID and Phone Numbers

ComparisonPhone NumberWSID
VariabilityUsers can change numbers; number becomes invalid after cancellationGenerally unchanged; can still be associated with old ID after number change
Deduplication AccuracyDepends on number staying the same; high duplication rateOnly one WSID per account; more accurate deduplication
Secondary ReachIf number is invalid, contact is lostEven if number is invalid, historical WSID can still match data
Storage CostLowHigh (requires additional field)

Use Cases for Exporting WSID

  • Community Deduplication: When merging WhatsApp contacts obtained from multiple channels, use WSID as the unique key to avoid duplicate additions.
  • User Profile Matching: Link WSID with existing leads in CRM to identify historical behavior even if the person changes their number.
  • API Secondary Verification: Before sending messages via WhatsApp Business API, check if WSID is still valid to save costs.
  • Cross-platform Data Synchronization: WSID can serve as an identification marker to transfer data between your own system and third-party tools.

How to Export WSID After Valid WA Number Detection?

On the KK-DATA platform, exporting WSID is very simple and requires no development skills. Here is the complete process.

Step 1: Submit a WA Valid Number Detection Task

  1. Log in to the Application Console and select the task type “WA Valid Detection.”
  2. Upload a list of numbers (supports CSV/TXT, one international format number per line), or use the “Global Number Generation” function to generate test numbers by country and number range.
  3. In the detection configuration, check the “Export WSID” option (it might be unchecked by default; please confirm manually).
  4. The system will estimate the task cost. Confirm and submit.

Step 2: Download the WSID Export File After Task Completion

  • Once the task is completed, you will receive a notification (you can also bind Telegram to receive alerts).
  • Click “Download Results” in the “Task Details” and select the export format (CSV or TXT).
  • The file will contain phone numbers, WSID, detection status, and other fields (see field descriptions below).

Step 3: Interpret WSID Fields and Clean Data

Example first few lines of a CSV (not real data):

phone,wsid,valid_status,detect_time
8613800138000,86abcXYZ123456,valid,2025-03-01 12:00:00
8613900139000,,invalid,2025-03-01 12:00:01
8613600136000,86def789012345,valid,2025-03-01 12:00:02
  • phone: Original number (international format).
  • wsid: Detected WSID; if the number is invalid or not detected, this field will be empty.
  • valid_status: valid indicates the number is a valid WhatsApp account; invalid indicates not registered or deactivated.
  • detect_time: Detection completion time.

After obtaining the data, use filtering tools to keep only rows where valid_status == valid and wsid is not empty, then import into CRM or proceed with next steps.


What Fields Are Included When Exporting WSID? Field Descriptions

Below are the common export fields in KK-DATA WA valid number detection results (actual fields may vary based on console configuration):

Field NameTypeDescription
phonestringInternational format phone number (e.g., 8613800138000)
wsidstringWhatsApp account ID, may be empty
valid_statusstringvalid / invalid / unknown
country_codestringCountry code (e.g., 86)
detect_timedatetimeDetection completion time
task_idstringAssociated task ID (for traceability)
raw_resultstringRaw detection result (for debugging)

Field Example

Typical CSV snippet (not real data):

phone,wsid,valid_status,detect_time
8613800138000,86abcXYZ123456,valid,2025-03-01 12:00:00
8613900139000,,invalid,2025-03-01 12:00:01

If the WSID field is empty, it usually means the number is not registered on WhatsApp or detection failed.

These fields can be directly integrated into your internal system. For example, use wsid as a unique identifier in CRM instead of phone numbers for deduplication and association.


Key Points for Exporting WSID via API Integration

For teams with technical capabilities, KK-DATA provides RESTful APIs to integrate detection and export into your own automated pipeline. Here are the basic call points.

1. Obtain API Key

Log in to the console → Personal Settings → API Management → Generate Token. Keep it secure. Never hardcode the Token in front-end code or public repositories.

2. Call Detection Task API

  • Endpoint: POST /api/v1/detect
  • Request Body (JSON):
    {
      "source_type": "whatsapp",
      "detect_type": "valid",
      "export_wsid": true,
      "numbers": ["8613800138000", "8613900139000"]
    }
  • Response: Returns task_id, which can be used to poll the task status.

3. Get Detection Results (Including WSID)

  • Endpoint: GET /api/v1/tasks/{task_id}/results
  • Response Format (JSON):
    [
      {
        "phone": "8613800138000",
        "wsid": "86abcXYZ123456",
        "valid_status": "valid",
        "detect_time": "2025-03-01T12:00:00Z"
      },
      ...
    ]

API Security Notes

  1. Token Protection: Never expose the API Token to clients or third parties. Store it in server-side environment variables.;
  2. Rate Limits: Free tier allows 60 requests per minute by default. Contact support for higher quotas.;
  3. Error Handling: When receiving a 429, back off and retry to avoid temporary account suspension.

4. Common Error Codes

HTTP Status CodeMeaningSuggested Action
200SuccessParse response body
401UnauthorizedCheck if Token is expired or malformed
429Too Many RequestsWait at least 1 second and retry
500Server ErrorRetry later or contact technical support

How to Avoid Duplicate Detection Waste When Batch Exporting WSID?

If you frequently process large numbers, different tasks likely contain the same numbers. KK-DATA’s built-in “Data Deduplication Repository” can automatically deduplicate and prevent repeated charges for the same number.

  • When creating a task, check “Enable Data Deduplication Repository.”
  • The system will check if the current number has been detected within the last 30 days (similar detection type). If it exists, the number will be skipped and not charged.
  • You can view historical detection records in the “Data Deduplication Repository” page, supporting filtering by number, task, and platform.

Best Practice: Export WSID results from each task and store them in your own database, while also enabling the deduplication repository on KK-DATA’s side. Double protection maximizes budget savings.


Is the WSID Export Feature Cost-Effective?

  • No Subscription Plans: KK-DATA charges per record; pay for what you use. No upfront monthly fees, suitable for small teams and burst demands.
  • WA Valid Detection Fee: Check the console for real-time pricing per number, generally lower than market average. WSID export is not charged separately — it’s just a field in the detection result.
  • Recharge Method: Only supports USDT (TRC20), minimum around 50 USDT, effective immediately upon arrival.
  • Insufficient Balance: New tasks cannot be submitted until you recharge.

Want to estimate costs? Before submitting a task, the console will display an estimated fee. Actual deduction occurs after task completion.


Frequently Asked Questions

Q: Can WSID exports be imported into third-party CRM?
A: Yes. CSV/TXT format is common structured data that can be directly imported into most CRM systems. However, it’s recommended to verify field mappings (e.g., phone corresponds to phone number, wsid corresponds to WhatsApp ID).

Q: Are WA valid number detection and WSID export billed separately?
A: No. Detection fee is charged per record. WSID export is an attached field in the detection result and is not charged separately. Specific unit price depends on the real-time pricing shown in the console.

Q: If the task result does not contain the WSID field, what could be the reason?
A: Possible reasons: ① The selected detection type does not include WSID export (e.g., only selected “valid” without checking “export wsid”); ② Number detection failed or is invalid, so no WSID is generated. Double-check configuration before submitting a task.

Q: Do I need additional permissions to export WSID via API?
A: You need to obtain an API key (Token) from the console to use the API. No additional approval is required. Please keep your Token secure and pay attention to request frequency to avoid rate limiting.

Q: Will the same number be charged twice when exporting WSID in different tasks?
A: If the “Data Deduplication Repository” is enabled, the system will automatically recognize previously detected numbers and skip them to avoid double charges. Frequent users are recommended to enable this feature.


We hope this guide helps you smoothly master the complete process of exporting valid WA numbers and WSID. If you have further questions, feel free to contact customer support @kkdata_cc or refer to the official User Documentation. Log in to the Application Console now to start your first detection task!