GET /repositories/{workspace}/{repo_slug}/pipelines
Find pipelines in a repository.
Note that unlike other endpoints in the Bitbucket API, this endpoint utilizes query parameters to allow filtering and sorting of returned results. See query parameters for specific details.
Servers
- https://api.bitbucket.org/2.0
Path parameters
Name | Type | Required | Description |
---|---|---|---|
repo_slug |
String | Yes |
The repository. |
workspace |
String | Yes |
This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces, for example |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
pagelen |
Integer | No |
The maximum number of results to return. Default value: 10 |
target.ref_name |
String | No |
The reference name to filter by. |
target.selector.type |
String | No |
The type of pipeline to filter by. Possible values:
|
sort |
String | No |
The attribute name to sort on. Possible values:
|
creator.uuid |
String | No |
The UUID of the creator of the pipeline to filter by. |
target.ref_type |
String | No |
The type of the reference to filter by. Possible values:
|
created_on |
String | No |
The creation date to filter by. |
status |
String | No |
The pipeline status to filter by. Possible values:
|
trigger_type |
String | No |
The trigger type to filter by. Possible values:
|
page |
Integer | No |
The page number of elements to retrieve. Default value: 1 |
target.selector.pattern |
String | No |
The pipeline pattern to filter by. |
target.commit.hash |
String | No |
The revision to filter by. |
target.branch |
String | No |
The name of the branch to filter by. |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.