Use "RequestCookie" in workflow inside "CallEndpoint" action

[ashishkumarc4u]

I need to use "RequestCookie" in my workflow to pull the logs from ZPE Nodegrid API received in response to AUTHENTICATION.
But I'm a bit confused how to put correct information in below format and there is no example to refer from.
Please if someone can help.

IBM suggested SYNTAX:

<RequestCookie name=” ${//cookies/<cookie_name>/name}” value=”${/< savePath>/cookies/ <cookie_name> /value}”>

What I'm using:

	<CallEndpoint url="${/host}" method="GET" savePath="/NodeGridLog" >
		<RequestCookie name=” ${/Nodegrid_auth/cookies/set-cookie/name}” value=”${/Nodegrid_auth/cookies/set-cookie/value}”>
		<RequestHeader name="Content-Type" value="application/json" />
		<RequestHeader name="Accept" value="application/json" />			
    </CallEndpoint>

Auth response (coockie) for reference:

{"cookies":{"status_code":200,"status_message":"OK","headers":{"server":"gunicorn","date":"Thu, 26 Jun 2025 11:29:43 GMT","content-type":"application/json","allow":"POST, OPTIONS","x-frame-options":"DENY","content-length":"601","x-content-type-options":"nosniff","referrer-policy":"same-origin","cross-origin-opener-policy":"same-origin","set-cookie":"session=xeovgi9sh19abcdefghijtyytborcdfghf5bz; expires=Thu, 26 Jun 2025 11:34:43 GMT; HttpOnly; Max-Age=300; Path=/; SameSite=Strict; Secure","strict-transport-security":"max-age=180; includeSubDomains; preload","access-control-allow-origin":"https://www.zpecloud.com","access-control-allow-methods":"GET, PUT, POST, DELETE, PATCH, OPTIONS","access-control-allow-headers":"Accept,Accept-Encoding,Authorization,Content-Type,DNT,Origin,User-Agent,X-Ijt,X-Requested-With,X-Xsrf-Token,Keep-Alive","access-control-allow-credentials":"true","vary":"Cookie, origin,Origin","via":"1.1 google","alt-svc":"h3=":443"; ma=2592000,h3-29=":443"; ma=2592000"},"body":{"id":3008,"username":"abcd@xyz.com","email":"abcd@xyz.com","first_name":"AB","last_name":"CD","type":"CA","first_access":false,"creation_type":"LOCAL","company":{"id":516,"access":true,"address":"730 7th Ave, 28th Floor, LA, LA 10175","business_name":"XYZ","contact_info":"mnop@xyz.com","company_icon":null,"enabled_on_premise":false,"monitoring":true,"sub_domain":null,"upgrade_configuration":true,"has_pending_devices":false},"companies_count":1,"setup_pwd":false,"session_timeout":300,"access_level":3}}}

[ChrisCollinsIBM]

Looking in the JSON response you provided - you're trying to access ${/Nodegrid_auth/cookies/set-cookie/name} which doesn't exist in that response.

"set-cookie":"session=xeovgi9sh19abcdefghijtyytborcdfghf5bz; expires=Thu, 26 Jun 2025 11:34:43 GMT; HttpOnly; Max-Age=300; Path=/; SameSite=Strict; Secure",

This is a single JSON element called set-cookie with a string value, no nested JSON. Where in the response above is the cookie name and cookie value you're trying to append to the next request?

---

There's also a leading space here after name=" that will possibly cause issues when you extract the correct name from somewhere.

<RequestCookie name=” ${/Nodegrid_auth/cookies/set-cookie/name}” value=”${/Nodegrid_auth/cookies/set-cookie/value}”>

[ashishkumarc4u]

Below is the CURL example extracted from POSTAMAN. I need to translate this in XML Workflow format.

curl --location 'https://api.zpecloud.com/company/logs?startDate=2025-05-22T03%3A00%3A51.231Z&endDate=2025-05-22T14%3A00%3A51.231Z&limit=10&search=%0A'
--header 'Cookie: XSRF-TOKEN=nvCoZShIPq9YqA3fm5zfSfVJEBemDk1W; session=xeovgi9sh19abcdefghijtyytborcdfghf5bz'

If I'm correct, I need to use below value, extracted from earlier shared Auth response (coockie) body.

session=xeovgi9sh19abcdefghijtyytborcdfghf5bz

Please if you can help me to write the correct 'RequestCookie' syntax in my CallEndpoint action.

<RequestCookie name=” ${//cookies/<cookie_name>/name}” value=”${/< savePath>/cookies/ <cookie_name> /value}”>

[ChrisCollinsIBM]

Presuming you need to specifically add a cookie with the name session, it would look something like this:

<RequestCookie name=”session" value=”${/response/cookies/session/value}”>

In the above example response would be where the savePath of the CallEndpoint was saved to.

In this example here you can see there would be a /savePath/cookies/ JSON element named /savePath/cookies/JSESSIONID/value that would return a token

{
   "status_code":200,
   "status_message":"OK",
   "headers":{
      "cache-control":"no-cache, no-store, must-revalidate",
      "strict-transport-security":"max-age=31536000;includeSubDomains",
      "x-frame-options":"DENY",
      "x-content-type-options":"nosniff",
      "accept-ranges":"bytes",
      "etag":"W/\"1972-1721901378000\"",
      "last-modified":"Thu, 25 Jul 2024 09:56:18 GMT",
      "vary":"accept-encoding",
      "content-type":"text/html",
      "transfer-encoding":"chunked",
      "date":"Tue, 03 Sep 2024 16:21:09 GMT",
      "keep-alive":"timeout=60",
      "connection":"keep-alive"
   },
   "body":"<*removed*>",
   "cookies":{
      "JSESSIONID":{
         "value":"🔐➡AQAAAAAAAAABUuq01zs3hUG7U3BGy9l3xAa3DtihKRSVRvLV9VmHLx19kzP5UIti27xbt/OiDQzyxIo9WWK7wEkn1kfq/Xg=⬅🔐",
         "name":"JSESSIONID",
         "path":"/",
         "domain":"test.example.net",
         "expiryDate":"Wed Sep 04 00:15:22 UTC 2024"
      }
   }
}

If the response in postman contains Set-Cookie values then those should be rendered under the /cookie element in the savePath

Maybe in your workflow test log the full /savePath/ response out or go check the /store/ec/universalrestapi/XX/state.json file for the log source and see the full response there also.