Test OTP delivery on staging
Pick a public number, submit it in your verification form and read the incoming message to confirm that your app sends the right text.
GET /api/v1/sms/numbers/{number}/messages
Receive SMS API
Receive SMS on public test numbers from many countries. List numbers, read the latest messages for a number and poll for new ones.
3 endpoints · 1 credit = $0.001. Each endpoint has its own credit cost, listed below. Calls that fail because of a service error are refunded.
API workspace and documentation
SMS Phone Numbers
Free Trial: 50 of 50 left
Select API to test:
List SMS Messages
Live SMS & OTP Verification Station
60 online numbers Physical SIM NetworkInstant SMS & OTP verification from real physical SIM networks worldwide (US, UK, NL, BE, FR, SE...).
Auto-sync active
Online Numbers
Loading live numbers...
Ready
?
?
No request yet. Run a test to see the actual response.
What you can build with the receive SMS API
The receive SMS API lists public phone numbers by country and returns the SMS they receive, from the tool above or from code. It is built for testing OTP and signup flows on staging, not for accounts you need to keep.
Check formats across countries
List numbers for different countries and confirm that your form accepts each number format and that the SMS arrives.
GET /api/v1/sms/numbers
Debug when you do not know which number received it
Read the latest messages across numbers to find the one your test triggered.
GET /api/v1/sms/messages
Guides: Test OTP flows with a receive SMS API · SMS OTP API: test an OTP login with Selenium and Python
Try it free, no account needed: Receive SMS online for OTP verification
How the receive SMS API works
-
1
List numbers
GET /api/v1/sms/numbers returns public numbers, optionally filtered by country.
-
2
Use a number in your test
Enter the exact number returned by the list in the form you are testing.
-
3
Read the messages
GET /api/v1/sms/numbers/{number}/messages returns the latest messages for that number.
Try the SMS Phone Numbers API with your own account
New accounts receive 1,000 credits after verification, enough for about 2000 calls to "List SMS Numbers".
Using SMS Phone Numbers
List available public numbers, optionally filtered by country.
Use the exact phone number returned by the list when reading messages. Message sources and pagination vary by provider.
Public inboxes may be shared. Do not use them for sensitive accounts or assume the number is exclusive to you.
Receive SMS API endpoints and pricing
OpenAPI 3.1 JSONSelect an operation above and open API & Docs for parameters and cURL, JavaScript, Python or PHP examples. The web tool uses your signed-in session; external integrations use a Bearer API key.
| Method | Endpoint | Cost |
|---|---|---|
| GET |
List SMS Numbers
/api/v1/sms/numbers
Try it
Helpful?
|
0.5 credit / request≈ $0.0005 |
| GET |
Get Messages for Number
/api/v1/sms/numbers/{number}/messages
Try it
Helpful?
|
1 credit / request≈ $0.001 |
| GET |
List SMS Messages
/api/v1/sms/messages
Try it
Helpful?
|
1 credit / request≈ $0.001 |
Receive SMS API: frequently asked questions
What is the receive SMS API?
It lists public phone numbers and returns the SMS they receive, so you can run OTP testing and SMS verification API flows on staging. The numbers are public, so use them for testing only.
Are the numbers private?
No. These are public numbers, so other people may see the same messages. Do not use them for sensitive or long-lived accounts.
Can I wait for a code in a single call?
Use the Verify API when you want to wait for a verification code and get it back in one call.
Will every service send SMS to these numbers?
Not guaranteed. Some services block public numbers, and message sources and pagination depend on the provider.
Is this an SMS OTP API I can use without renting a number?
Yes. This SMS OTP API lists shared public numbers and returns the messages they receive, so you do not rent or provision a number the way you would with a provider such as Twilio or Vonage. The trade-off is that the numbers are public, so use them for testing on staging only.
How is it billed?
Per request. Listing numbers and reading messages have different prices, shown in the endpoint table below. New accounts receive 1,000 credits after verification.
Before integrating
Live and example data
Check the Live or Sandbox label before running. Examples demonstrate the response structure and do not guarantee live service status.
Credits and limits
Pricing depends on the endpoint and billable units. Failed live requests are not replaced with billable examples. Check your account limits before running repeated requests.
View pricingHandling errors
Keep the request ID for troubleshooting. For 429, respect Retry-After when provided. If a create or delete request loses its connection, check the resource state before retrying.
Related APIs
All APIs-
Verification Codes
1 endpointsWait for a verification code to arrive and get it back in a single call, with polling and timeouts handled by AxioAPI.
View Verification Codes API → -
Temporary Email
6 endpointsCreate disposable inboxes, read incoming messages, rotate addresses and delete inboxes when you are done. Available through the AxioAPI REST API.
View Temporary Email API → -
Email Validation
4 endpointsCheck whether an address is well-formed, disposable or deliverable. Validate one email, a batch, or run an async job over thousands.
View Email Validation API →
Often used together: OTP API · Temp Mail API · Email Validation API
Ready to integrate the SMS Phone Numbers API? Create an account and get your API key in minutes.