Skip to main content
Test numbers require team beta access. When the beta is offered on the Numbers page, a team owner or admin selects Join on its beta row, reviews the terms and selects Accept and join. Inspector has its own beta row. Without test-number access, creation and use are blocked; existing numbers remain available for review, stopping, and deletion. You need:
  • A development project UUID.
  • An team key with sessions:read and sessions:manage.
Keep the credential on a trusted server.

​
1. Create a testing number

projectId is required. country is optional and defaults to US; it accepts one of the 243 WhatsApp-supported ISO alpha-2 codes published in the request schema. The response contains the generated testing-session identifier. A successful response means the number’s API-controlled device is connected and ready to receive commands. The linked device reconnects after service or app restarts without another pairing step. Removing the testing number invalidates that device. Testing numbers can message only active testing numbers in the same project. A send request can identify the recipient as an E.164 number such as +15551234567 in conversation.phoneNumber. A malformed, unknown, stopped, removed, or cross-project recipient returns the same 404 Not Found result and no chat, contact, or message is created. Testing-number API sessions simulate the public messaging and session command surface, including media, message mutations, acknowledgements, contacts, groups, channels, presence, privacy, profiles, labels, and business catalogs. The API-controlled device and Inspector read the same simulated account and conversation state. Message requests remain available while the recipient’s Inspector companion is closed and deliver after it reconnects. Removing the recipient cancels pending delivery. No simulated command contacts WhatsApp or a real recipient.

​
2. List the project’s sessions

Select the row whose generated session identifier matches the create response. Testing-number rows have testMode: true.

​
3. Remove the testing number

Removal closes an open Inspector session and clears the number’s simulated state before returning success. If the number cannot be closed, the request fails and leaves the record available for a retry. Removal is permanent. Use the generated Platform API endpoint pages for the complete request, response, authorization, and error schemas.

​
Where to go next

Number pool

List and manage testing numbers.

Inspector ownership and devices

Open a testing session in the desktop app.

Sandbox limits

Review throughput and included data.

Authentication

Review credential audiences and scopes.