Trigger last pipeline using the API

Question

Hello, I want to trigger a pipeline from one repository of my organization using the API. I had a look at this post and this documentation but it doesn't seem to work. So I went to https://bitbucket.org/account/settings/app-passwords/ and I created an app password with all the rights (I guess I just need "write" on "pipeline" but this is just for testing). Then I used this curl command: curl -X POST -is -u : \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories///pipelines/ \ -d ' { "target": { "ref_type": "branch", "type": "pipeline_ref_target", "ref_name": "master" } }' But it gives me a 401 error. if I use my account password, the query is successful and it triggers the pipeline. For obvious security reasons I don't want to use my password to trigger a pipeline through a script, but just a token I can revoke at any time. Any idea how I can trigger the pipeline using the API?

Oleksandr Kyrdan · Answer

@[deleted] thanks, good suggestion.

It's a good practice to rotate generated secrets periodically.

As an alternative you could use an OAuth consumer on Bitbucket Cloud.

If you’d like to suggest feature to improve, please, find the appropriate ticket in the list of existing tickets, vote for them or create a new suggestion request with type Suggestion.

Best regards,
Oleksandr Kyrdan

unknown · Answer

So, I managed to make it work with the same CuRL request as the one posted earlier, but with: username: "" of the creator of the team password: app password generated by the creator of the team, with Pipelines Write and Repositories Read permissions. I don't get why we can't create API token at a repository level, using a user account for it doesn't make sense when we trigger the pipeline from an application. Furthermore, the token gives access to every repository of the user, which is way too extensive, it should be possible to restrict the token to only 1 repo. If the token is compromised, anyone can trigger pipelines for the whole organization... Regards, Francois

Oleksandr Kyrdan · Answer

@[deleted]

Please take a look at trigger pipeline pipe source code under the hood, as it's open sourced )

Here are payload structure and parameters required for programmatically API interaction from the Python code.

Note! Remember to check the Pipelines Write and Repositories Read permissions when generating the app password.

If you have right permissions to the team workspace app password should work.

Cheers,
Oleksandr Kyrdan