Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to add responders in create customer request via API

abhishek
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2025

 

Hi everyone,

I’m using the Jira Service Management Cloud REST API to create customer requests (POST /rest/servicedeskapi/request) and need to include Responders (customfield_10044). According to the metadata (GET /rest/servicedeskapi/servicedesk/{serviceDeskId}/requesttype/{requestTypeId}/field'), the schema is:

{
"fieldId": "customfield_10044",
"name": "Responders",
"description": "",
"required": false,
"defaultValues": [],
"validValues": [],
"jiraSchema": {
"type": "array",
"items": "string",
"custom": "com.atlassian.jira.modules.servicemanagement.responders-entity:responders-entity-field-cftype",
"customId": 10044
},
"visible": true
}

 

I added responders in  UI-created issues and then tried to get them, the response shows:
(GET /rest/servicedeskapi/request/{issue_type})

{
"fieldId": "customfield_10044",
"label": "Responders",
"value": [
{
"ari": "ari:cloud:identity::user/userId",
"name": "name",
"type": "user",
"avatarUrl": "url"
},
{
"ari": "ari:cloud:identity::user/userID",
"name": "name",
"type": "user",
"avatarUrl": "url"
}
]
}

 However, when I attempt to send this via API:

"customfield_10044": [
{
"id": "userID"
},
{
"id": "userID"
}
]

 

Jira is giving 201 created but returns an empty array in the response.

{
"fieldId": "customfield_10044",
"label": "Responders",
"value": []
}


I understand <value> should be a user identifier, but I'm missing something. Reading the API response suggests each responder must be formatted as:

 

{ "accountId": "<id>" }

 

or

 

{ "id": "<id>" }

 

So the request should look like:

 

"customfield_10044": [ { "accountId": "userId" }, { "accountId": "userId" } ]
or 
"customfield_10044": [ { "id": "userId" }, { "id": "userId" } ]
or 
"customfield_10044": [ { "name": "userId" }, { "name": "userId" } ]
or
"customfield_10044": [ { "value": "userId" }, { "value": "userId" } ]

However, all of these still result in an empty array in the issue response.

Questions:

  1. What is the correct structure to send customfield_10044 in the requestFieldValues payload?

  2. Does the accountId need special formatting (with/without prefix)?

  3. Are there permission or feature flags needed to allow API population of responders?

Any guidance on how to make Responders populate correctly via the Service Desk API would be greatly appreciated!

1 answer

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2025

HI @abhishek 

Welcome to the community.

To set a multi-user picker custom field in Jira via the API, you need to use the accountId of the users, not their names or display names. The field value should be an array of account IDs.

{
"fields": {
"customfield_XXXXX": [
{
"accountId": "user_account_id_1"
},
{
"accountId": "user_account_id_2"
}
]
}
}

Replace XXXXX with the actual ID of your custom field, and user_account_id_1, user_account_id_2 with the account IDs of the users you want to add to the field.

You can retrieve the account ID of a user by using the Jira REST API or by querying the user using their email or name.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events