Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
RESTlet URLs
A few weeks ago we got moved to a new data center.
We did not make any changes to our RESTlet URLs, and they all continued to work. So we were hitting URLs like https://rest.netsuite.com/app/site/hosting/restlet.nl?script=123&deploy=1
Everything was working until last night, when all of our RESTlet integrations started failing with a 401 "Unauthorized".
We realized the URL endpoints have changed, so now they look like this: https://rest.na3.netsuite.com/app/site/hosting/restlet.nl?script=123&deploy=1
Prior to our account migration, we went through a big exercise to avoid hardcoded URLs within Netsuite. The theory being that we could be dynamically switched from the na3 datacenter at any time. So are we really supposed to be using hardcoded na3 URLs in our RESTlet integrations? What is the best practice here to avoid future disruption?