Skip to content

Atlassian: Find users for picker

Atlassian userSearch.findUsersForPicker: arguments, response, policy and SDK examples.

← User search operations · Get started

Operation atlassian.findusersforpicker

Provider route: GET /{cloudId}/rest/api/3/user/picker. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/atlassian with npm, or alter-sdk-atlassian with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { AtlassianIntegration } from "@alter-ai/atlassian";
async function execute(input: Parameters<AtlassianIntegration["userSearch"]["findUsersForPicker"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new AtlassianIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.userSearch.findUsersForPicker(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_atlassian import AtlassianIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = AtlassianIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.user_search.find_users_for_picker(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.cloudIdstringRequired within parentPattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
queryobjectRequired within parentAdditional keys: not allowed
query.querystringRequired within parent
query.maxResultsintegerOptionalDefault: 50
Format: int32
query.showAvatarbooleanOptionalDefault: false
query.excludearrayOptional
query.exclude[]stringEach item
query.excludeAccountIdsarrayOptional
query.excludeAccountIds[]stringEach item
query.avatarSizestringOptional
query.excludeConnectUsersbooleanOptionalDefault: false

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Find users for picker — response body

Referenced models: Find users for picker — response body

Find users for picker — response body
FieldTypePresenceDescription and constraints
$objectRootThe list of users found in a search, including header text (Showing X of Y matching users) and total of matched users.
headerJSONOptional
header (anyOf 1)stringAlternativeHeader text indicating the number of users in the response and the total number of users found in the search.
header (anyOf 2)nullAlternative
totalJSONOptional
total (anyOf 1)JSONAlternative
total (anyOf 1) (anyOf 1)integerAlternativeThe total number of users found in the search.
Format: int32
total (anyOf 1) (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
total (anyOf 2)nullAlternative
usersJSONOptional
users (anyOf 1)arrayAlternative
users (anyOf 1)[]ModelEach itemExpand Find users for picker — response body — users array item
users (anyOf 2)nullAlternative

Referenced models: Find users for picker — response body — users array item

Find users for picker — response body — users array item
FieldTypePresenceDescription and constraints
$objectRootA user found in a search.
accountIdJSONOptional
accountId (anyOf 1)stringAlternativeThe account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e05b22cc7d4ef5*.
accountId (anyOf 2)nullAlternative
accountTypeJSONOptional
accountType (anyOf 1)stringAlternativeThe user account type. Can take the following values:

* `atlassian` regular Atlassian user account
* `app` system account used for Connect applications and OAuth to represent external systems
* `customer` Jira Service Desk account representing an external service desk
Known values: atlassian, app, customer, unknown
accountType (anyOf 2)nullAlternative
avatarUrlJSONOptional
avatarUrl (anyOf 1)stringAlternativeThe avatar URL of the user.
Format: uri
avatarUrl (anyOf 2)nullAlternative
displayNameJSONOptional
displayName (anyOf 1)stringAlternativeThe display name of the user. Depending on the user’s privacy setting, this may be returned as null.
displayName (anyOf 2)nullAlternative
htmlJSONOptional
html (anyOf 1)stringAlternativeThe display name, email address, and key of the user with the matched query string highlighted with the HTML bold tag.
html (anyOf 2)nullAlternative
keyJSONOptional
key (anyOf 1)stringAlternativeThis property is no longer available. See the [deprecation notice](https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/) for details.
key (anyOf 2)nullAlternative
nameJSONOptional
name (anyOf 1)stringAlternativeThis property is no longer available . See the [deprecation notice](https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/) for details.
name (anyOf 2)nullAlternative

SDK function policy ID: atlassian.findusersforpicker. Catalog operation: findusersforpicker. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["read:jira-user"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.