Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
No Limits. Just possibilities.
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.
NetSuite launches new wholesale distributions solution in Japan in January 2026!

NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.

Register Now
NetSuite 2026.1 Release Notes - This document summarizes the changes to NetSuite between 2026.1 and the previous release.

Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.

RESTlet Authorization Issue

edited Dec 2, 2019 5:51PM in SuiteCloud / Customization 7 comments

For what it's worth (and I know it's not a lot of help but...), I was running into continuous Unauthorized 401 issues trying to authenticate with RESTlet. After a lot of head scratching, it turned out to be the password. For whatever reason, it would not accept the password even though in the Employee record, it accepted it without issue (even identified it as strong).

I don't know exactly what part of the password was causing the error. The password started with a number (9), and had an @ character and a dot (.) along with upper case letters, lower case letters and a few additional numbers. I changed it to start with a letter and removed the @ character, but everything else was the same and it worked. Go figure...

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders