REST API ATTACHMENT

[arwinblones]

Hi Dev,

I want to know if how does it work? im currently trying to implement the attachment api binary and multipart but i got always an error upon my end. Here is the script i used for manual testing on my end in the background script i always got this error

No URIs provided, removing all URI matcher rules

the user has the following roles. These roles are setup since i build my own ebonding integration which is working correctly i just reuse the user as my authentication user. I dont have a problem regarding on this one since its working fine on my ebonding integrations only the main problem is the rest api attachment integration.

Can you identify what causing it to become 401 and removing all URI matcher rules?

No URIs provided, removing all URI matcher rules
*** Script: Attachment Untitled Diagram.png sent. Status: 401 

[Ankur Bawiskar]

@arwinblones 

Also error 401 means incorrect username and password

that user should have write Access to that incident table.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[arwinblones]

Hi @Ankur Bawiskar , 

I tried the credentials (username and password), also the acl sn_incident_write but still 401.

[arwinblones]

@Ankur Bawiskar , the get in rest api attachment is working but when post and patch is used its status is 401 and 400

i tried as well the admin as user and password but still get is only functional. I think ServiceNow have a problem on this since both users are working fine because if it doesnt work my EBonding shouldnt be able to create another incident from another instance

[Ankur Bawiskar]

@arwinblones 

it should work fine

Could you tell what's your exact business requirement?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏