Bitbucket private repository using API tokens

Hi!

Bitbucket App passwords have been replaced by API tokens since September 9, 2025. New App passwords cannot be created, and instead we need to use API tokens. I’ve configured the credentials as usual (following the instructions in this blog post), using the API token instead of the password. Nevertheless, it doesn’t seem to work.

Do you know how can I make API tokens work? Or do we need an update of nextflow on this feature?

Hi @Irene_PD, I’m happy to report support for this was added in the 25.08.0-edge version of Nextflow (in this commit: Add support for Bitbucket API tokens instead of access tokens (#6337)… · nextflow-io/nextflow@1d73b87 · GitHub )

So upgrading your version of Nextflow should make this work. Note that if you are using Seqera Platform, the Cloud version should already have it, but any Enterprise version would need to be updated accordingly.

I hope this helps!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.