Check WhatsApp numbers at scale.

Whether the number is registered on WhatsApp, whether it is a business account and its profile name if it has one, the kind of number it is, the country it belongs to, and a link that opens a chat with it. One request, one response, no polling.

Definitive answers only. Registered and not registered each use one validation from your monthly allowance, because you can act on both. A number we cannot parse, a request over your rate limit, and a check no upstream could answer all cost nothing. On Growth and higher plans, unused validations roll over into the next month, once; Starter's allowance resets each month.

No. You never connect a WhatsApp number, a WhatsApp Business account or a Cloud API app. You create an account, choose a plan and create an API key, the checks run on our side, and your own sending setup stays as it is.

No. You can upload a spreadsheet or check a single number in the web dashboard, check the numbers on any web page with the Chrome extension, or ask your AI assistant to do it. The API is there for teams that want the check built into their own software.

They are used to run the checks you ask for, and we do not sell or rent them. The result of a single lookup is cached for at most 30 days. A bulk list and its results are deleted 30 days after the job finishes or stops, and the billing record of each validation never includes the number. During a check, the number goes only to the provider that performs the WhatsApp lookup, for that check only.

Between roughly 300 and 800 milliseconds end to end, including the upstream lookup. It varies with the destination country, which is why it is quoted as a range rather than as an average or a percentile. That is fast enough to sit inside a signup form.

Up to your plan's file limit per job, from 5,000 unique numbers on Starter to 300,000 on Enterprise, uploaded as a CSV of up to 100 MB or an Excel file of up to 25 MB. Duplicates are removed before anything is billed. Files run at a pace set by the plan, from 4 rows per minute on Starter to 20 on Enterprise, so a full file takes from about 21 hours on Starter to about 10½ days on Enterprise; start a large list well before the send. That is slower than the real-time API on purpose: the API keeps its priority, and a file is queued out of process so it cannot slow your real-time calls down. The pace is shared by an account's running files and is a ceiling, so a busy platform can make a file take longer. Starter and Growth process one file at a time, Business two and Enterprise three, and further uploads wait in line and start by themselves, from 3 on Starter to 20 on Enterprise. A file spends the monthly allowance but none of the hour or day caps. Check a running file about once a minute, because each status read counts against your per-minute request limit.

You get an explicit unknown and no charge, never a guess. Treat it as unknown and let the contact through. Recording it as not registered is how a real customer gets dropped from a list over a bad minute on our side.

Between 5 and 300 requests per minute depending on the plan, plus hourly, daily and monthly ceilings on validation calls. The figures for every plan are on the pricing page, and in a table at /pricing.md. The per-minute limit is shared by everything an account opens: the real-time endpoint, bulk submission, status polling and the MCP server, and extra keys do not multiply it. The hour and day ceilings count real-time validation calls only, so polling a job never spends them. Going over any limit returns a 429 that carries that limit's real remaining window.

Checks pause when your allowance runs out. You can wait for renewal or upgrade your plan. Upgrades apply when payment clears, with only the prorated difference charged. On Business and Enterprise you can also request extra validations from the dashboard, in blocks of 100,000 at €99 / $99 each (in your subscription currency) and up to 1,000,000 at a time. We review requests within one business day. Extra validations are spent after your monthly allowance, through the API and file uploads alike.

Extra validations never expire. Use them while you have a paid plan, after your monthly allowance. If your subscription lapses, we keep your unused extra validations until you subscribe again. Closing your account removes them. Your plan's processing limits and file sizes still apply.

Yes, through our MCP server. It is a published npm package under an MIT licence with the source on GitHub, so you can read exactly what it sends before you point an agent at it. It uses the same API key and draws on the same monthly allowance, so an agent cannot run up a bill outside the limits you already set.