What Are Priority Requests and When Should You Use Them?

We have a constant demand for SMS verification, and there are some extremely popular services, such as WhatsApp, Telegram, and Venmo, that may sell out very quickly. When inventory reaches zero and the system shows "0 available", it becomes impossible to get a number using a Standard Request. You will receive a "No numbers available, retry later" error.

So, what can be done then? There is a proper solution: Priority Requests are the correct and efficient way to obtain numbers when demand is high and stock is limited.

Here is how it works:

You create a Priority Request and choose a markup percentage, which is an additional amount you are willing to pay above the base price. The request is then placed with "Awaiting MDN" status and a lifetime of 30 minutes.

As soon as a new number becomes available for the selected service, the system automatically assigns it to the user with the highest markup. If several users have the same markup, the number is assigned to the user who placed the request first.

This system ensures fairness while rewarding users who are willing to pay more for faster access, instead of rewarding aggressive API spamming.

But can't I get the same number at the base price by using API spamming?

In short, no. Sometimes users attempt to gain an advantage by sending hundreds of API requests per second. They believe this "smart" strategy will help them catch the next available high-demand number faster.

In reality, this approach is a bad idea, since if there are other users at the same time using priority requests, the number will be assigned to them instead of users sending spammy requests.

Since this behavior puts unnecessary load on the platform and negatively affects other users, our system actively detects abusive request patterns and will automatically block accounts that spam the API. As a result, these users waste time and risk losing access instead of improving their success rate.

How Priority Requests Work in Practice

A Priority Request remains active for up to 30 minutes. During this time, the system continuously waits for a new number to appear in inventory. If a number becomes available, it is instantly assigned according to priority rules.

If no number becomes available within 30 minutes, the request is automatically canceled and any reserved funds are released back to your balance.

Important Rules

There is no upfront charge for placing a Priority Request. You only pay if and when you successfully receive an online SMS message on the assigned number.

If you want to reuse a number later, you can do so at a reduced cost, which is 50 percent of the base price (not the marked-up price you paid to get the number in the first place).

If you are not receiving numbers even with Priority Requests, it usually means that other users are offering higher markups. In that case, increasing your markup improves your chances.

Technical Information for API Users

We provide two ways to track Priority Requests programmatically:

  • A special "request_status" API endpoint that allows you to check the status of requests in "Awaiting MDN" state.
  • A webhook event called "priority_request", which is triggered immediately when a number is assigned.

This allows full automation for users integrating SMS verification flows into their systems.

When Should I Use Priority Requests?

Priority Requests are recommended when:

  • The service is out of stock (inventory shows zero)
  • You are working with high-demand platforms such as WhatsApp, Telegram, or similar services
  • You need a faster and more reliable chance of receiving a number for SMS verification or OTP

Do You Have a Video Guide?

Yes, we have prepared a YouTube video explaining how Priority Requests work and how to use them effectively. We recommend watching it to understand the process in detail before placing requests.