GET /rest/api/2/project/search

Returns a paginated list of projects visible to the user.

This operation can be accessed anonymously.

Permissions required: Projects are returned only where the user has one of:

Servers

Query parameters

Name Type Required Description
startAt Integer No

The index of the first item to return in a page of results (page offset).

Default value: 0

maxResults Integer No

The maximum number of items to return per page.

Default value: 50

action String No

Filter results by projects for which the user can:

  • view the project, meaning that they have one of the following permissions:

    • Browse projects project permission for the project.
    • Administer projects project permission for the project.
    • Administer Jira global permission.
  • browse the project, meaning that they have the Browse projects project permission for the project.

  • edit the project, meaning that they have one of the following permissions:

    • Administer projects project permission for the project.
    • Administer Jira global permission.
  • create the project, meaning that they have the Create issues project permission for the project in which the issue is created.

Possible values:

  • "browse"
  • "create"
  • "edit"
  • "view"

Default value: "view"

properties[] Array No

EXPERIMENTAL. A list of project properties to return for the project. This parameter accepts a comma-separated list.

expand String No

Use expand to include additional information in the response. This parameter accepts a comma-separated list. Expanded options include:

  • description Returns the project description.
  • projectKeys Returns all project keys associated with a project.
  • lead Returns information about the project lead.
  • issueTypes Returns all issue types associated with the project.
  • url Returns the URL associated with the project.
  • insight EXPERIMENTAL. Returns the insight details of total issue count and last issue update time for the project.
categoryId Integer No

The ID of the project's category. A complete list of category IDs is found using the Get all project categories operation.

status[] Array No

EXPERIMENTAL. Filter results by project status:

  • live Search live projects.
  • archived Search archived projects.
  • deleted Search deleted projects, those in the recycle bin.
id[] Array No

The project IDs to filter the results by. To include multiple IDs, provide an ampersand-separated list. For example, id=10000&id=10001. Up to 50 project IDs can be provided.

propertyQuery String No

EXPERIMENTAL. A query string used to search properties. The query string cannot be specified using a JSON object. For example, to search for the value of nested from {"something":{"nested":1,"other":2}} use [thepropertykey].something.nested=1. Note that the propertyQuery key is enclosed in square brackets to enable searching where the propertyQuery key includes dot (.) or equals (=) characters. Note that thepropertykey is only returned when included in properties.

query String No

Filter the results using a literal string. Projects with a matching key or name are returned (case insensitive).

orderBy String No

Order the results by a field.

  • category Sorts by project category. A complete list of category IDs is found using Get all project categories.
  • issueCount Sorts by the total number of issues in each project.
  • key Sorts by project key.
  • lastIssueUpdatedTime Sorts by the last issue update time.
  • name Sorts by project name.
  • owner Sorts by project lead.
  • archivedDate EXPERIMENTAL. Sorts by project archived date.
  • deletedDate EXPERIMENTAL. Sorts by project deleted date.

Possible values:

  • "-deletedDate"
  • "-category"
  • "+owner"
  • "+archivedDate"
  • "+lastIssueUpdatedDate"
  • "-archivedDate"
  • "issueCount"
  • "+issueCount"
  • "owner"
  • "archivedDate"
  • "-owner"
  • "+category"
  • "-issueCount"
  • "-lastIssueUpdatedDate"
  • "deletedDate"
  • "key"
  • "lastIssueUpdatedDate"
  • "name"
  • "-name"
  • "category"
  • "+key"
  • "+deletedDate"
  • "+name"
  • "-key"

Default value: "key"

keys[] Array No

The project keys to filter the results by. To include multiple keys, provide an ampersand-separated list. For example, keys=PA&keys=PB. Up to 50 project keys can be provided.

typeKey String No

Orders results by the project type. This parameter accepts a comma-separated list. Valid values are business, service_desk, and software.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.