Domains and IP Addresses
Ensure your integration is always communicating with MyMobileAPI
Your integration must be able to reach the relevant MyMobileAPI fully qualified domain names for it to function properly. Depending on which API you have chosen and how your integration operates, you may need add them to a whitelist.
To help your integration operate securely, it must also verify that it’s communicating with the relevant MyMobileAPI domain through one of our listed IP addresses below.
If your integration also receives webhooks from MyMobileAPI, you should ensure these events originate from one of our webhook IP addresses.
MyMobileAPI Domains and IP Address List
MyMobileAPI interacts with your integration using one or more of the below fully qualified domain names:
For reference we have included the IPs per domain.
MyMobileAPI domains:
Domain | Current IPs | New IPs (from 20 Oct 2025) |
---|---|---|
ftp.mymobileapi.com | 105.29.233.5 | 102.205.165.57 102.205.167.57 |
rest.mymobileapi.com | 105.29.233.5 | 102.205.165.58 102.205.167.58 |
mymobileapi.com | 105.29.233.5 | 102.205.165.59 102.205.167.59 |
legacy.mymobileapi.com | 105.29.233.10 | 102.205.165.60 102.205.167.60 |
Always use the fully qualified domain name to contact our APIs — never an IP address.
Webhook Notifications
The full list of IP addresses that webhook notifications may come from is:
Current IPs | New IPs (from 20 Oct 2025) |
---|---|
105.29.233.17 105.29.233.2 | 102.205.164.49 102.205.166.49 |
Updated 10 days ago