# URL Encode JSONPath Variables in HTTP Request

**URL:** <https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, sailpoint-identity-security\
**Created:** [February 28, 2023, 1:28am UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634 "2023-02-28T01:28:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brendonmurphy](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/brendonmurphy/32/19167_2.png) [@brendonmurphy](https://developer.sailpoint.com/discuss/u/brendonmurphy)\
**Post date:** [February 28, 2023, 1:28am UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634/1 "2023-02-28T01:28:30Z")

</div>

Hello All,

I was working on a workflow to get a TemporaryAccessPassword from AAD then get a secure link to email to new starters.  
However it seems that when you use JSON Path to get values it doesn’t encode them properly. I came across [Support for Inline Variable for HTTP Request URL Field](https://developer.sailpoint.com/discuss/t/support-for-inline-variable-for-http-request-url-field/6250) that says its not supported currently.

Is that still the case, is a fix coming soon potentially? Does anyone have a work around we that would use to bypass this.

When I use special characters as a basic string, they will be encoded in the query parameters properly.

[TAPPWPush20230228.txt](https://developer.sailpoint.com/discuss/uploads/short-url/vJjQsbOIcvMLp9kVz3w9RhA0JJ6.txt) (3.7 KB)

We are reaching out to other resources too currently.

Regards  
Brendon

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [February 28, 2023, 2:15pm UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634/2 "2023-02-28T14:15:46Z")

</div>

Hi Brendon,

I see the inline variable that you are trying to use:

`"url": "https://graph.microsoft.com/beta/users/{{$.getAccounts.accounts[?(@.sourceName == \"Azure AD - Members\")].attributes.userPrincipalName}}/authentication/temporaryAccessPassMethods"`

Inline variables that use a filter operation are not yet supported, but it is on the roadmap to implement this functionality.

---

<div class="post-metadata">

**Author:** ![brendonmurphy](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/brendonmurphy/32/19167_2.png) [@brendonmurphy](https://developer.sailpoint.com/discuss/u/brendonmurphy)\
**Post date:** [March 5, 2023, 9:52pm UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634/3 "2023-03-05T21:52:42Z")

</div>

Hey Colin

Nah its the next one with PWPush, but I have spoken to support/our CSM and the current feedback is full support for inline variables is Q2 this year. With potentially some partial functionality before that.

I’ll just close this off for now.

Regards  
Brendon

---

<div class="post-metadata">

**Author:** ![sharvari](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@sharvari](https://developer.sailpoint.com/discuss/u/sharvari)\
**Post date:** [May 2, 2023, 1:01pm UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634/4 "2023-05-02T13:01:21Z")

</div>

Hi @colin_mckibben  
Is this functionality available now? any update?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [July 19, 2023, 2:24pm UTC](https://developer.sailpoint.com/discuss/t/url-encode-jsonpath-variables-in-http-request/8634/5 "2023-07-19T14:24:25Z")

</div>

Closed on July 19, 2023, 2:24pm UTC


