GET /workspaces/{workspace}/permissions/repositories/{repo_slug}
Returns an object for the repository permission of each user in the requested repository.
Permissions returned are effective permissions: the highest level of permission the user has. This does not distinguish between direct and indirect (group) privileges.
Only users with admin permission for the repository may access this resource.
Permissions can be:
adminwriteread
Results may be further filtered or sorted by user, or permission by adding the following query string parameters:
q=permission>"read"sort=user.display_name
Note that the query parameter values need to be URL escaped so that =
would become %3D.
Servers
- https://api.bitbucket.org/2.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
repo_slug |
String | Yes |
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: |
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 |
|---|---|---|---|
q |
String | No |
Query string to narrow down the response as per filtering and sorting. |
sort |
String | No |
Name of a response property sort the result by as per filtering and sorting. |
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.