API IP rules and whitelisting

Which IP addresses may use your API credentials, how an address gets on your list, and how you keep or block it. This applies to every API: the HTTP API (SMS, voice, WhatsApp and email), the XML API, the legacy API and API v2.

The short version. You do not need to send us your IP address. Call the API with your correct credentials: the address you call from is added to your list and we email you about it. In the email, or in the portal, you keep the address or block it. A blocked address is refused, even with the right credentials.

1. How an address gets on your list

Every account has its own list of the IP addresses its API credentials are used from. The list covers all your API keys and your username / password together.

The request comes fromWhat happens
An address on your list, allowedThe request is served.
An address you blockedThe request is refused before anything is sent or charged. See what a refused request looks like.
A new address, during your first 15 days The address is added and the request is served. We email you that it was added automatically, and why.
A new address, after your first 15 days The address is added and the request is served. We email you that your API is being used from a new address and ask you to keep it or block it.
Any address, with wrong credentialsThe request fails as usual (authentication error). The address is not added to your list.

So there is no approval queue to wait in. An address is whitelisted the moment you use it with the right credentials, and you stay in control because you are told every time.

2. Existing customers and new customers

Both get the same 15 days in which every new address is added automatically. Only the starting day differs.

Existing customers
accounts that were using the API before these rules (November 2026)
New customers
accounts registered after that
What you must do first Nothing. Keep calling the API as you do today. Nothing. Make your first API call from the server you will use.
The 15 days start With your first API request after the rules were introduced. With your first API request.
During the 15 days Every address that uses your correct credentials is added and served. You get one email per new address so you can check it.
After the 15 days A new address is still added and served, and the email asks you to confirm it: keep or block.
Using one API v2 key from several addresses Sign in to the portal once and enter the code we email you. That verifies your account, which this needs. See API v2 keys. Your email is verified when you register, so this works as soon as you have SMS credits.

If you are an existing customer and you see an email about an address you have used for years, that is expected: it is the first time we have seen it under these rules. Choose Keep.

3. The email: keep or block

The email goes to the email address on your account. It shows the IP address, the API that was called and the time, and has one button: Keep or block this IP address.

We send at most 10 of these emails per account per day. Further new addresses on the same day are still recorded and shown in the portal.

You do not recognise the address? Block it, then change your API key and password straight away: someone else has your credentials.

4. Managing addresses in the portal

Sign in and open API Management → API IP addresses. The page lists every address your API has been used from, with its state, the API it called and when it was first and last used.

  1. Whitelist an address in advance. Enter the IP address, choose Allow and a period, and save. Do this before you move to a new server, and no email is needed for that address.
  2. Block an address. Choose Block on its row, or add it with Block. It is refused from the next request.
  3. Change your mind. Allow a blocked address, block an allowed one, or remove a row. A removed address counts as new the next time it is used.

An address that nobody reviewed and that has not been used for 90 days is removed from the list automatically.

5. API v2 keys

An API key (used with Authorization: Bearer, X-API-Key or api_key on /api/v2) also has its own IP list, on top of your account list.

SituationWhat happens
First successful request with a new keyThe address is added to the key's list automatically.
The same key from a further address, and your account has SMS credits and a verified email or mobile number The address is added to the key's list and the request is served. You get the usual email to keep or block it.
The same key from a further address, and your account has no credits or is not verified HTTP 403, IP address not allowed. Add the address yourself (below), or verify your account and top up.
An address you blocked on your account listHTTP 403, whatever the key's own list says.

What counts as verified: you entered a sign-in code or used the sign-in link we sent to your email or mobile, or you verified your email when you registered, or you verified a test mobile number with an OTP. An account that was moved from the previous platform and has never signed in to the portal is not verified yet: sign in once.

To add an address to a key yourself: open API Management, choose the key, then IP Whitelisting. Add the address, or press Add My Current IP to add the address you are on now.

The HTTP API, the XML API, the email API and the legacy API (username / password or api_key parameter) have no per-key list. For them only your account list in sections 1 to 4 applies.

6. What a refused request looks like

A request from an address you blocked is refused like this. Nothing is sent and nothing is charged.

APIHTTP statusResponse
HTTP API, XML API, email API
/httpapi/…, /xmlapi/…, /httpemailapi/…
200The plain text -45
Legacy API
/api/secure_api/…
403JSON with "error_code": -45
API v2
/api/v2/…
403JSON with "error": "Forbidden"
# Legacy API
{
  "success": false,
  "error_code": -45,
  "error_message": "Requests from IP address 203.0.113.10 are blocked for this account."
}

# API v2: address blocked on your account list
{
  "success": false,
  "error": "Forbidden",
  "message": "Requests from IP address 203.0.113.10 are blocked for this account."
}

# API v2: address not on the key's own list
{
  "success": false,
  "error": "Forbidden",
  "message": "IP address not allowed. Please whitelist your IP address to access the API."
}

To fix it: open API IP addresses and allow the address, or use the link in the email. The change applies from the next request.

7. Blocks after repeated failed attempts

Separately from your own list, an address that keeps sending wrong credentials in a short time is blocked for the whole platform. This stops password guessing and floods before they reach your account.

8. Common questions

Do I have to ask support to whitelist my IP?

No. Use the API with the right credentials and the address is added. You can also add it in advance in the portal.

My server's IP address changes (cloud, auto-scaling, dynamic IP). What should I do?

Nothing breaks: each new address is added and served. You will get an email for each new address, up to 10 a day. If that is too many, ask support to switch the IP notices off for your account; a fixed outgoing IP (NAT gateway) is the better fix.

I did not get the email.

Check the email address on your account and your spam folder. The address is in the portal list either way, and you can keep or block it there.

I blocked my own server by mistake.

Open API IP addresses in the portal and choose Allow on that row.

Does a wrong password add or block my address on my list?

No. Only a request with correct credentials adds an address. Many wrong attempts in a short time can trigger the platform block in section 7.

Is this the same as the sign-in check on the portal?

No. The portal has its own rule: signing in from a new network asks for a code sent to your email. This page is about API requests only.

My API IP addresses Back to API docs

How can we help?

Sales
Support
Billing
Technical
CAPTCHA
Type the 4 characters shown in the image