Regular Verification Introduction

The authorization is simple, you go to your account page and there you can generate an API Key. This API Key gives access to your account, so watch out with whom you share it! Once you have created an API Key, you can proceed to the functions that the API offers. The functions that are offered can be viewed below. Each of these functions can be invoked by providing the correct parameters with a GET request. The server will always give status code 200, only the body of the response will differ.

This is the legacy API. It is still live and nothing on this page has changed or will change. New integrations should use the current API instead: JSON throughout, real HTTP status codes, the verification code extracted for you, cursor pagination and webhooks. Your existing API key already works there as a bearer token, so there is nothing to migrate before you try it.

Endpoint: /api/makeorder?key=APIKEY&serviceId=SERVICEID&country=NL Method: GET

To make an order you need to send a request to the endpoint above providing the right serviceId. To view the serviceIds go to your account page and click 'Show API ID's On Service Page'.

Parameter	Description
key	Your API Key. (Required)
serviceId	The ID of the service you wish to make an order for. (Required)
country	Specify the country you wish the number to be from. Options: USA, NL or UK (Optional NL by default)

Possible Responses:

NO_PHONE_AVAILABLE - There is unfortunately no phone available for the specified service.
ORDER_ALREADY_OPEN_{ORDER_ID} - There is an order already open. Please finish or cancel this one before making a new order.
NO_BALANCE - There is unfortunately not enough balance on your account for this order.

Success:
ORDER_ID_{ORDER_ID}_NUMBER_{PHONE_NUMBER} - Your order has been successfully made.

Endpoint: /api/getsms?key=APIKEY&orderId=ORDERID Method: GET

With this method you can see the SMS that came in for the order.

Parameter	Description
key	Your API Key. (Required)
orderId	The ID of the order you wish to check if a SMS came in. (Required)

Possible Responses:

ORDER_EXPIRED - The order has been canceled or has been expired.
WAITING - The order is still open waiting for a SMS to come in.

Success:
SUCCESS_{SMS_CONTENT} - Your SMS has been successfully received.

Endpoint: /api/cancelorder?key=APIKEY&orderId=ORDERID Method: GET

With this method you can cancel an active order.

Parameter	Description
key	Your API Key. (Required)
orderId	The ID of the order you wish to cancel. (Required)

Possible Responses:

ORDER_ALREADY_EXPIRED - The order has already been expired.
ORDER_ALREADY_COMPLETED - The order has already been completed.

Success:
ORDER_CANCELED - Your order has been canceled.

Endpoint: /api/skipnumber?key=APIKEY&orderId=ORDERID Method: GET

With this method you can skip a number of an active order so you dont get it again in the future.

Parameter	Description
key	Your API Key. (Required)
orderId	The ID of the order you wish to skip the number on. (Required)

Possible Responses:

ORDER_ALREADY_EXPIRED - The order has already been expired.
ORDER_ALREADY_COMPLETED - The order has already been completed.

Success:
NUMBER_SKIPPED_ORDER_CANCELED - Your order has been canceled and the number has been skipped. You can make a new order with a fresh number.

Endpoint: /api/getbalance?key=APIKEY Method: GET

With this method you can get your current balance in USD.

Parameter	Description
key	Your API Key. (Required)

Possible Responses:

{YOUR_BALANCE} - Your current balance in USD

Endpoint: /api/reuse?key=APIKEY&orderId=ORDERID Method: GET

In case you wish to use the same number again for the same service as an already completed order you can use this API call.
NOTE: Re-using is only available for a very short time after the initial order. (A few hours usually)

Parameter	Description
key	Your API Key. (Required)
orderId	The ID of the order you already completed and wish to re-use. (Required)

Possible Responses:

NUMBER_OFFLINE - The number has been replaced and is gone.
ORDER_ALREADY_OPEN_{ORDER_ID} - There is an order already open. Please finish or cancel this one before making a new order.
NO_BALANCE - There is unfortunately not enough balance on your account for this order.

Success:
ORDER_ID_{ORDER_ID}_NUMBER_{PHONE_NUMBER} - Your order has been successfully made.

Endpoint: /api/services?country=NL Method: GET

Retrieve the list of available services together with their prices for a given country. This endpoint is public — an API key is optional and only needed if you want your account's custom pricing applied. Use it to look up the id (serviceId) of each service before calling MakeOrder.

Parameter	Description
country	The country to return prices for. Options: `NL`, `UK`, `USA`, `DE` (`GB` and `US` are accepted as aliases for UK and USA). If omitted or invalid, the response lists only service IDs and titles, without prices. (Optional)
key	Your API Key. When provided, any custom prices configured for your account are applied to the response. (Optional)

Possible Responses:

Success (without a valid country): a JSON array of services with only their ID and title.

For example:


[
  { "id": 1, "title": "WhatsApp" },
  { "id": 2, "title": "Telegram" }
]

Success (with a valid country): a JSON array of services including pricing.

For example:


[
  {
    "id": 1,
    "title": "WhatsApp",
    "price": 0.5,
    "price_original": 0.5,
    "currency": "EUR",
    "formatted_price": "€0.50"
  },
  {
    "id": 2,
    "title": "Telegram",
    "price": 0.45,
    "price_original": 0.45,
    "currency": "EUR",
    "formatted_price": "€0.45"
  }
]

Where id is the serviceId used by MakeOrder, price is the price for the selected country, price_original is the base price before currency conversion, currency is the currency code of the returned price, and formatted_price is the display-ready price string.

Long Term Numbers Introduction

The long-term rentals API is different from the regular verification API. The reason for this is that this API is more complex and has been developed at a later stage.

Endpoint: /api/rental/new Method: POST

Purchase a new rental.

Parameter	Description
key	Your API Key. (Required)
country	The country you wish the rental to be from (NL/UK) (Required)
package	Rental duration package. Options: `1m` (1 Month, €15), `3m` (3 Months, €30), `6m` (6 Months, €50), `1y` (1 Year, €70). Defaults to `1m` if not specified. (Optional)
auto_renew	Enable auto-renewal. (Optional, defaults to true)

Possible Responses:

NO_STOCK - There is unfortunately no phone available for the specified country.
NO_BALANCE - There is unfortunately not enough balance on your account for this order.
INVALID_PACKAGE - The specified package is not valid.

Success:
You will get a JSON response with success and the details about the new rental number.

For example:


{
  "success": true,
  "contract_id": 34405,
  "package": "3m",
  "auto_renew": "true",
  "expire_on": "2026-06-22T12:57:03.000000Z",
  "phone_number": "07684563067",
  "country": "UK"
}

Endpoint: /api/rental/extend Method: POST

Extend a rental contract. You can choose a package to extend with a different duration than the original purchase.

Parameter	Description
key	Your API Key. (Required)
contract_id	The ID of the rental you wish to extend. (Required)
package	Extension package. Options: `1m`, `3m`, `6m`, `1y`. Defaults to `1m` if not specified. This also updates the auto-renewal package. (Optional)

Possible Responses:

NUMBER_EXPIRED - The contract has already been expired.
NO_BALANCE - You dont have balance to extend the number.
INVALID_PACKAGE - The specified package is not valid.

Success:
You will get a JSON response with success and the new expire of the rental number.

For example:


{
  "success": true,
  "package": "3m",
  "new_expire": "2026-09-22T12:57:03.000000Z"
}

Endpoint: /api/rental/edit Method: POST

Enable or disable autorenew.

Parameter	Description
key	Your API Key. (Required)
contract_id	The ID of the rental you wish to edit. (Required)
auto_renew	The new value of the auto renew setting (true/false) (Required)

Possible Responses:

Success:
You will get a JSON response with success and the new auto renew setting of the rental number.

For example:


{
  "success": true,
  "auto_renew": false
}

Endpoint: /api/rental/view Method: POST

Get all the information and SMS of the rental number

Parameter	Description
key	Your API Key. (Required)
contract_id	The ID of the rental you wish to view. (Required)

Possible Responses:

Success:
You will get a JSON response with success and the info of the rental number.

For example:


{
    "success": true,
    "contract_id": 33405,
    "phone_number": "07684563067",
    "country": "UK",
    "package": "3m",
    "renewal_package": "3m",
    "auto_renew": false,
    "expire_on": "2026-09-22T12:57:03.000000Z",
    "received_sms": [
        {
            "id": 1,
            "sender": "Uber",
            "body": "Your Uber code is 0183. Never share this code.",
            "receive_date": "2023-08-02T14:30:23.000000Z"
        },
        {
            "id": 2,
            "sender": "SinchVerify",
            "body": "Your Tinder code is 417097 Don’t share @tinder.com #417097",
            "receive_date": "2023-08-02T14:30:42.000000Z"
        }
    ]
}

Legacy API (v1)

Regular Verification Introduction

Endpoint: /api/makeorder?key=APIKEY&serviceId=SERVICEID&country=NL Method: GET

Possible Responses:

Endpoint: /api/getsms?key=APIKEY&orderId=ORDERID Method: GET

Possible Responses:

Endpoint: /api/cancelorder?key=APIKEY&orderId=ORDERID Method: GET

Possible Responses:

Endpoint: /api/skipnumber?key=APIKEY&orderId=ORDERID Method: GET

Possible Responses:

Endpoint: /api/getbalance?key=APIKEY Method: GET

Possible Responses:

Endpoint: /api/reuse?key=APIKEY&orderId=ORDERID Method: GET

Possible Responses:

Endpoint: /api/services?country=NL Method: GET

Possible Responses:

Long Term Numbers Introduction

Endpoint: /api/rental/new Method: POST

Possible Responses:

Endpoint: /api/rental/extend Method: POST

Possible Responses:

Endpoint: /api/rental/edit Method: POST

Possible Responses:

Endpoint: /api/rental/view Method: POST

Possible Responses: