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.
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
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?