How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Jira User search API

This resource represents various ways to search for and find users. Use it to obtain list of users including users assignable to projects and issues, users with permissions, user lists for pickup fields, and user lists generated using structured queries. Note that the operations in this resource only return users found within the first 1000 users.

Jira User search API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User Search. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

This API exposes 8 operations across 8 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df.

Requests are made against a single base URL, https://your-domain.atlassian.net.

8 operations 8 paths 14 schemas 8 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
Base URL
https://your-domain.atlassian.net/rest/api/2
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Jira User search API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 186 scopes. It accepts HTTP basic authentication (basicAuth).

  • OAuth2 — OAuth2 scopes for Jira
  • basicAuth — You can access this resource via basic auth.

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 8 GET. Each is listed below with its method, path, parameters, and response codes.

User Search 8

This resource represents various ways to search for and find users. Use it to obtain list of users including users assignable to projects and issues, users with permissions, user…

GET
/rest/api/3/user/assignable/multiProjectSearch
Find users assignable to projects
findBulkAssignableUsers 6 params → 200400401404429
GET
/rest/api/3/user/assignable/search
Find users assignable to issues
findAssignableUsers 13 params → 200400401404429
GET
/rest/api/3/user/permission/search
Find users with permissions
findUsersWithAllPermissions 8 params → 200400401403404429
GET
/rest/api/3/user/picker
Find users for picker
findUsersForPicker 7 params → 200400401429
GET
/rest/api/3/user/search
Find users
findUsers 6 params → 200400401429
GET
/rest/api/3/user/search/query
Find users by query
findUsersByQuery 3 params → 200400401403408
GET
/rest/api/3/user/search/query/key
Find user keys by query
findUserKeysByQuery 3 params → 200400401403408
GET
/rest/api/3/user/viewissue/search
Find users with browse permission
findUsersWithBrowsePermission 7 params → 200400401404429

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are User (16 properties), ApplicationRole (14 properties), PageBeanUser (7 properties), UserPickerUser (7 properties). Each schema is shown below with its type and property counts.

ErrorCollection
object
Error messages from an operation.
3 properties
UserKey
object
List of user account IDs.
2 properties
FoundUsers
object
The list of users found in a search, including header text (Showing X of Y matching users) and total of matched users.
3 properties
UserPickerUser
object
A user found in a search.
7 properties
GroupName
object
Details about a group.
3 properties
ListWrapperCallbackGroupName
object
ApplicationRole
object
Details of an application role.
14 properties
PageBeanUser
object
A page of items.
7 properties
ListWrapperCallbackApplicationRole
object
SimpleListWrapperGroupName
object
5 properties
User
object
A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: User record deleted from Atlassian: T…
16 properties
AvatarUrlsBean
object
4 properties
SimpleListWrapperApplicationRole
object
5 properties
PageBeanUserKey
object
A page of items.
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-user-search-api-openapi.yml Raw ↑

Other APIs Jira publishes across the network.

Jira Cloud Platform REST API v2
Jira Service Management Operations REST API
Jira Align REST API
Jira Customer Service Management REST API
Jira Issue Comments API
Jira Issue Priorities API
Jira Issue Search API
Jira Issue Statuses API
Jira Issue Transitions API
Jira Issue Types API
Jira Issues API
Jira Projects API
Where this information came from

This is an independent, third-party profile of Jira User search API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.