Service Catalog API (order_now) Not Respecting sysparm_requested_for

[mattmurdock]

Hi Everyone,

We are running into an issue with the Service Catalog API on our Zurich instance and are hoping the community can help us figure out what is going on.

What we are trying to do

We are performing an integration that submits catalog item requests using the:

POST /api/sn_sc/servicecatalog/items/{sys_id}/order_now

The integration includes a valid user’s sys_id in the sysparm_requested_for parameter so that the RITM is generated with that user listed in the requested_for field.

What we expect

According to the documentation, the value passed in sysparm_requested_for should populate the Requested For field on both the sc_req_item records.

What is actually happening

Even though the payload includes a valid user sys_id the requested_for on the RITM is being set to the integration user that is submitting the request. This occurs consistently on every request.

 

What we have already validated

• We are on the Zurich release.
• We are using Basic Auth with a dedicated integration account.
• The sys_id sent in sysparm_requested_for maps to a valid user in sys_user.
• We checked for catalog item workflows, business rules, Flow Designer actions, client scripts, and any other logic that could overwrite requested_for post‑submission — we did not find anything.
• The integration user has the following roles:
  catalog, itil, user_admin, snc_internal, sn_request_read.
• We reviewed the RITM's update history and confirmed that there is only a single record in the audit table for the RITM related to the requested_for field. This indicates that there are no workflows or automations occurring after the initial record creation that is modifying this field.
• We submitted the same request through the API Explorer, using the identical sysparm_requested_for sys_id, and in that scenario the RITM was created correctly with the expected user in the requested_for field.

Goal / Question

How can we get the sysparm_requested_for parameter to be honored correctly when using the order_now API?

Any insights or confirmation from others who have used this API successfully in Zurich would be greatly appreciated.

Thank you!

[Ankur Bawiskar]

@mattmurdock 

requested_for field must be having a default value as logged in user and hence this issue is coming.

check this link and see if that helps

sysparm_requested_for isn't working 

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