REST API's not returning response ?

[Gaurav Kumar15]

Hi Team,

I am using the OOB rest API for incident table :-

https://instance.service-now.com/api/now/table/incident

I have few doubts :-

1. For creating incident via REST API , if we have to pass the username of Caller

'caller_id':'cb3230342bb3d60083dac7ac17da15af'

e.g :- This i am using for populating a user, is there any other way of populating caller, because 3rd party tool might not aware of the sys id of user record. So how rest will create the incident for some other user.

2. When i am hitting this Rest API, then the incident is getting created but Response is showing as empty in other tool. Does anyone knows why it comes as empty.

Thanks & Regards,

Gaurav Kumar

[markraichuk]

We are doing some testing the Import Set REST API in Jakarta to interface with the Incident table via the imp_notification import set table.   We have added ACLs to the imp_notification table along with a new role which has been assigned to a user account that will be sending REST API requests.   While the record in the import set table (imp_notification) is created along with the new incident, we are getting a blank REST response.     When we enable the REST API debug, I do see the following warning message:

WARNING *** WARNING *** #1490 [REST API] ImportSetAPIService : Created record can't be read. No Record found

But I cannot figure out where the issue lies.   I understand the rest_service role has been deprecated and is no longer need, but I cannot figure out what additional roles are needed to obtain the regular REST response mentioned (https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/integrate/inbound-rest/reference...).   If I send the same REST request using an admin account, the response comes back fine.   I've also tried assigning the itil role to the user, but still an empty response.   I've also reviewed https://hi.service-now.com/kb_view.do?sysparm_article=KB0596738, but not sure what ACL they are referring to deactivate and think this KB may be dated given it's still referenceing the rest_service.

Any help would be greatly appreciated.

[Chuck Tomasi]

Thanks Mark,

It definitely sounds like a permissions issue. If the import set record is getting created, you are half way there. Does the user account being used for the REST request have access to create in the target table (incident)?

[markraichuk]

Chuck,

Thank you for the quick reply and for the guidance.   I've seen you on numerous posts and you definitely have an expert-level knowledge.

After lots of trial and error, I discovered that the import_transformer role is required, which seems odd as the transformation runs just fine without, it's just the response is empty which I guess contains the transformation information.

Thanks again for the reply.

[Chuck Tomasi]

Hi Mark,

Thanks for the update. I was reading through the roles and understood import_transformer to be someone who can manage the transform maps, not necessarily "run" the transform. Poor description IMHO.

As you figured out the answer, you might want to mark your answer as "Correct" to help others in the future find the answer should they have similar questions.

[Gaurav Kumar15]

Thanks Chuck, i will go through the video