I'm trying to pull out the accountId based on an email address using automation. * My web request url is /rest/api/3/user/search?query={{issue.customfield_10094.urlEncode}} * Http method: GET * Web response body: Issue data (Jira format) * Headers* Authorization: basic * Accept: application/json When i try to validate web request config with a project key, I see the payload with my custom field value: "customfield_10094": "my_email@email.com", But when I log {{webResponses.body.first.accountId}}, it turns up empty. What am I doing wrong?

@DLLPGF I have the same API using this: * My web request url is /rest/api/3/user/search?query={{issue.customfield_XXXX.urlEncode}} * Http method: GET * Web request body: EMPTY * Headers* Authorization: basic * Accept: application/json And finally I'm get the web response using this variable: {{webResponse.body.accountId}} Seeing your details, maybe you just need to avoid to get first in your web request response. Have you tried this?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rest API - Not getting accountId web response

DL_XM

I'm trying to pull out the accountId based on an email address using automation.

My web request url is <jira_url>/rest/api/3/user/search?query={{issue.customfield_10094.urlEncode}}
Http method: GET
Web response body: Issue data (Jira format)
Headers
1. Authorization: basic <api_token>
2. Accept: application/json

When i try to validate web request config with a project key, I see the payload with my custom field value:

"customfield_10094": "my_email@email.com",

But when I log {{webResponses.body.first.accountId}}, it turns up empty. What am I doing wrong?

Accepted answers

Fernando Eugênio da Silva_2ddgg8

@DLLPGF

I have the same API using this:

My web request url is <jira_url>/rest/api/3/user/search?query={{issue.customfield_XXXX.urlEncode}}
Http method: GET
Web request body: EMPTY
Headers
1. Authorization: basic <api_token>
2. Accept: application/json

And finally I'm get the web response using this variable: {{webResponse.body.accountId}}

Seeing your details, maybe you just need to avoid to get first in your web request response.

Have you tried this?

All comments

Fernando Eugênio da Silva_2ddgg8

@DLLPGF

I have the same API using this:

My web request url is <jira_url>/rest/api/3/user/search?query={{issue.customfield_XXXX.urlEncode}}
Http method: GET
Web request body: EMPTY
Headers
1. Authorization: basic <api_token>
2. Accept: application/json

And finally I'm get the web response using this variable: {{webResponse.body.accountId}}

Seeing your details, maybe you just need to avoid to get first in your web request response.

Have you tried this?

DL_XM

I updated with Web request body: EMPTY and {{webResponse.body.accountId}}, but still getting an empty value.

Audit logs:

Action details:

USER CONDITION

The following issues passed:

<key>

SEND WEB REQUEST

Successfully published web request

LOG ACTION

Log

my_email@email.com (customfield_10094) and <EMPTY> {{webResponse.body.accountId}}

DL_XM

I've also tried {{webResponse.body.emailAddress}} and {{webResponse.body.accountType}} and it returns nothing.

When I do run <jira_url>/rest/api/3/user/search?query=my_email@email.com, I get a json response and can see accountId, emailAddress, accountType and lots of other data.

DL_XM

I have a suspicion that my headers are not correct, even though I get a 200 response. Can you give me an example of how it should be?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation