title: NetSuite SuiteTalk REST Web Services - Invalid Login Attempt
body: <p>I am trying to use the NetSuite SuiteTalk REST Web Services to access NetSuite CRM data.</p>
  
  <p>I have the access up and working in production.  Able to retrieve record data and metadata.</p>
  
  <p>I am now trying to set up access in the sandbox for more in-depth testing.</p>
  
  <p>In the sandbox I have:
  - Enabled rest web services
  - Enabled token based authentication
  - Given user concurrent web services permission
  - Given user Log in using access tokens permission
  - Created an integration
  - Created an access token</p>
  
  <p>All of these actions mirrored what was done in production.</p>
  
  <p>When I attempt any kind of GET to the web service, I receive a 401 - Invalid login attempt.</p>
  
  <p>When I check the Login Audit Trail, I don't see any record of the GET attempt, failed or otherwise.</p>
  
  <p>Is there something of a systemic nature that I have to do additionally in the sandbox to enable rest web services?  Above and beyond enabling it in SuiteCloud/SuiteTalk?</p>
  
  <p>The fact that I see absolutely nothing in the audit trail makes me believe that something is still "turned off".</p>
  
  <p>===> 4/4/2020 Update</p>
  
  <p>ed14 and Nihkil,</p>
  
  <p>Thank you for your responses, and sorry for the delay in responding back.</p>
  
  <p>The hyphen to underscore in the realm did not help me unfortunately.</p>
  
  <p>Let me recap recent attempts:</p>
  
  <p>1) Started by verifying that REST API testing in production still works.</p>
  
  <p>2) The sandbox was refreshed by a CRM admin. The application was still there, but my access token was not. I created a new one in the sandbox.</p>
  
  <p>Is it possible to delete the application? I cannot see any way to do that.</p>
  
  <p>3) Tested with existing Consumer Token and new Access Token. Got the same response as from my first post: "title": "Invalid login attempt, for more details see Login Audit Trail.",</p>
  
  <p>4) Tested by slightly modifying the URL to make sure I was not going to a black hole somewhere. It gave me the expected error.</p>
  
  <p>5) Tested by modifying the realm: Realm 9999999-sb4 to Realm 9999999_sb4 It gave me an error which leads me to believe that my original realm is correct: "title": "An unexpected error occurred. Error ID: k8hd8pqej3unxblmaoik",</p>
  
  <p>Again, none of the tests show up in anywhere in the audit log as a failed attempt.</p>
  
  <p>Not sure where to go from here? Delete the sandbox application (if possible) and start again? Or new application in sandbox?</p>
  
  <p>Thanks for any and all help.</p>
  
  <p>Bryan Hunt</p>