Happy Monday All! I am trying to create a Payment...
# general
s
Happy Monday All! I am trying to create a Payment Method using API into Netsuite. I have created a Netsuite authenticator with All credentials and logged in using the Admin role. The admin role has FULL permission on Payment Methods and AccountingLists. However when triggering the API getting the following error: We have checked our integration user in Netsuite as well but could not find which role it is associated with. Can anyone please help on this urgent issue ? Looking for some help in a API error : "title": "Forbidden", "status": 403, "o:errorDetails": [ { "detail": "Permission violation: Permission Violation: You need the 'Accounting Lists' permission to access this page. Please contact your account administrator.", "o:errorCode": "INSUFFICIENT_PERMISSION" } ] }
b
its pretty unusual to not know which roles are on assigned to an employee
its found on the employee record, and integration users tend not to have too many
that said, the Login Audit Trail is where you would track logins, which include rest api requests
go find a login at the same time the request was made
s
I know what role is assigned to the employee which is ADMIN role and that role has both PayementMethod and AccountingLIst access to FULL. Anything else I am missing here ?
b
your error message disagrees
your employee probably has multiple roles, and the login token is not using administrator
s
Thanks let me recheck
Hi @battk I checked and its the same Admin role of the user . Is there anything else That needs to be checked ?
My User did have multiple roles though but the log showed the Admin as the recent accessed onein audit trail
Btw is there a way to find which user is assigned to the login token ? As I checked theother role ( non Admin) and that also has access to both PayementMethod and AccountingLIst
b
you dont care about the most recently accessed role
you care about the login at the same time as the request
theoretically you can use the request uri column is you want to make sure that the request's url matches a web services related one
but the vast majority of the time you only need the timing