Introduction

The Numestri API rents phone numbers for SMS verification, hands you the code when it arrives, and covers long-term rentals and email accounts.

Embed
Preview of the card
<a href="https://numestri.com/docs/introduction"><img src="https://numestri.com/docs/_api/public/orgs/25229885-9620-4c08-bd2e-a0d0d74ac8b6/spaces/ef21e0c3-966d-4b03-b6d2-e66d449835d4/pages/137056b5-be94-4ebc-9f3a-ddd07392eb16/social-card.svg?v=3e7ae33eec8b" alt="Introduction" width="600" height="315"></a>

The Numestri API does over HTTP everything the dashboard does: find a number for a platform and country, buy it, receive the verification code, and rent numbers or buy email accounts in bulk.

https://numestri.com/api/v1

You can explore it right now, without signing up: the catalogue, quotes, rental pricing and email products are public.

curl https://numestri.com/api/v1/catalog/platforms
Quickstart
Browse, get a quote, then buy and receive your first code — every call shown.
Authentication
What is public, what needs a key, how to create one, and the rate limits.
The catalogue
Walk platforms → countries → providers → options, one scoped call at a time.
Ordering numbers
Buy the best option, one provider's, or exactly the option you picked.

What needs a key

Without a key

With a key

Browse the catalogue: platforms, countries, providers, options, prices and stock

Everything on the left, priced for your account

Quote a platform and country

Buy numbers, check and cancel orders

See rental countries, terms and prices

Rent, read, extend, reset and return numbers

See email products and prices

Buy email accounts and read their inboxes

Download the OpenAPI document

Check your balance

Without a key you see the public list prices. With one you see your own account's prices, which can differ if your account has negotiated pricing. The full table, the rate limits and how to create a key are in Authentication.

How it behaves

  • GET or POST, your choice. Every endpoint accepts both. Parameters can go in the query string, a form body, or a JSON body.

  • JSON out. Every response is JSON. Failures have success: 0; see Errors.

  • Exact ids. Platforms are ids like whatsapp, countries are ISO codes like US. Names and aliases are refused rather than guessed, so an order can never land on the wrong service. Get ids from the catalogue.

  • Prices are set by us, at order time. You never send a price. The amount charged is worked out on our side when you order — the same price the catalogue and quotes showed your account. Pass max_price to refuse anything above what you expect.

  • Prepaid. Orders draw down your balance at the moment you buy. A number that never receives a code is refunded automatically.

  • Familiar shape. The ordering endpoints keep the request and response shape most verification APIs use (/purchase/sms, /sms/check, order_id, type: "OUT_OF_STOCK"), so an existing integration usually moves over with a new base URL and key.

Machine-readable

The full OpenAPI 3.1 description is at /api/v1/openapi.json — public, no key needed. The API reference section of these docs is generated from it, so it always matches the API that's running.

Updated