Scripted REST API or OOTB API

[Joshua Cassity]

We have a requirement to allow an external system to submit an item out on our service catalog.   Here's what we are doing using the 'Buy Item' resource using the 'SN_SC' api:

1. Peoplesoft initiates a REST call to begin an onboarding catalog item once approval is gathered for the hire. (this is working)

2. RITM is created and populated with that employee's information. (this is working)

3. Response is sent back to Peoplesoft with the RITM number to save on the approval record.

Item 3 poses an issue for us because the response only gives the REQ number and we really need the RITM number to be sent back in the response (which they'll store in their system) instead because if they need to update the RITM with new information (say Mary's last name changes during onboarding because she got married or her first day was going to be Monday but is now Friday, etc...).

Is the only way to handle such a thing is to create a scripted REST api (which we've never done before so it'll be a learning curve for me) or is there some other mechanism in the header or body to specify what needs to go back in the response?

Thanks for your assistance.

[Joshua Cassity]

They get a response back and I'm pretty sure they can configure it to be XML. The main issue is they are getting the REQ number and sys_id but we need them, for simplicity and ease of making future calls, to get the RITM number that was generated.

[Shital Revandka]

Hello,

I need to create a Webservice API where input is: Sys ID of any record and output is: all *related* active records to that sys id. The relationships between the tables is maintained in Relationships under system definition.

Could you please guide me how to implement this? Sample code would be great.

Input: Sys ID of the record
Output: All *RELATED* active records from *VARIOUS* tables (in the following JSON format):
{
"result": [
{
"Sys ID": "5520267",
"CI Name": "Record 1",
"Table Name": "u_table_a"
},
{
"Sys ID": "5520367",
"CI Name": "Record 2",
"Table Name": "u_table_a"
},
{
"Sys ID": "8331210",
"CI Name": "Record 1",
"Table Name": "u_table_b"
},
{
"Sys ID": "8321210",
"CI Name": "Record 2",
"Table Name": "u_table_b"
},
{
"Sys ID": "3042006",
"CI Name": "Record 3",
"Table Name": "u_table_b"
},
{
"Sys ID": "4509847",
"CI Name": "Record 1",
"Table Name": ""u_table_c"
}
{
"Sys ID": "4509247",
"CI Name": "Record 2",
"Table Name": ""u_table_c"
}
]
}

[DaSmith9]

Once you have the REQ # from the first response, I would think you would just initiate a GET call from PeopleSoft to SN to get any RITM associated to the REQ (returned from the first call) and Item in question? (sysparm_query & encoded query)

Then you would have a second response with the RITM record details and could then store the RITM number/reference as well.

Thanks,

Daniel

[Joshua Cassity]

I'd really prefer them not to have to made multiple calls versus getting what they need back in a single call.

[andrew_venables]

You haven't said which API you are interacting with at the moment?

If its the Table API then you can add additional return fields as per the docs: https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/integrate/inbound_rest/concept/c_...

If its the Service Catalog API then there are numerous endpoints that should give you what you want: https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/integrate/inbound-rest/concept/c...