By osirisr
I’m creating a backend API for a mobile app. Instead of mydomain.com/api … is it okay and technically viable, for example, to use 415.21.23.235/api instead? Are there any security risks, downtime, disadvantages, etc?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
That’s technically fine. One disadvantage / risk that I can think of is in the event that you wanted to move to different VPS (new droplet or different host all together). This would issue a new IP address making your original URL invalid so anyone using your API would have to make an update. With the domain this wouldn’t be an issue since the IP change would happen at the DNS level.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.