# Problem with integration Bitbucket cloud and Jenkins using BB workspace access token **URL:** \ **Category:** Using Jenkins\ **Created:** [September 5, 2024, 4:00am UTC](https://community.jenkins.io/t/problem-with-integration-bitbucket-cloud-and-jenkins-using-bb-workspace-access-token/19121 "2024-09-05T04:00:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![paymankouhi](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@paymankouhi](https://community.jenkins.io/u/paymankouhi)\ **Post date:** [September 5, 2024, 4:00am UTC](https://community.jenkins.io/t/problem-with-integration-bitbucket-cloud-and-jenkins-using-bb-workspace-access-token/19121/1 "2024-09-05T04:00:20Z")
Hi All, In Bitbucket Cloud and Jenkins integration we have faced with API rate limit issue, we were using app password but it didn’t work since the rate limit reached very quick! So the plan is breaking down the jobs into different access tokens, I created workspace access token but I don’t know how I can use it in our Jenkins jobs, for example in a freestyle I just tried to create a new credential using username/password and filled out the field as below: `'x-token-auth':'WorkspaceAccessToken'` I put x-token-auth as username and WorkspaceAccessToken as password, but in job config I get the following error: **The selected credentials do not have permission to determine whether “workspace” does or does not exist.** Any idea? Also regarding API rate limit issue any idea is highly appreciated! Thanks! ## Jenkins setup: Jenkins: 2.346.1 OS: Linux - 3.10.0-1160.42.2.el7.x86\_64 Java: 1.8.0\_171 - Oracle Corporation (Java HotSpot™ 64-Bit Server VM) ace-editor:1.1 amazon-ecr:1.7 ansicolor:1.0.1 ant:1.12 antisamy-markup-formatter:2.4 apache-httpcomponents-client-4-api:4.5.13-1.0 artifactory:3.13.2 authentication-tokens:1.4 aws-credentials:191.vcb\_f183ce58b\_9 aws-java-sdk:1.12.101-300.vc09c7be9cb57 aws-java-sdk-cloudformation:1.12.101-300.vc09c7be9cb57 aws-java-sdk-codebuild:1.12.101-300.vc09c7be9cb57 aws-java-sdk-ec2:1.12.163-315.v2b\_716ec8e4df aws-java-sdk-ecr:1.12.101-300.vc09c7be9cb57 aws-java-sdk-ecs:1.12.101-300.vc09c7be9cb57 aws-java-sdk-elasticbeanstalk:1.12.101-300.vc09c7be9cb57 aws-java-sdk-iam:1.12.101-300.vc09c7be9cb57 aws-java-sdk-logs:1.12.101-300.vc09c7be9cb57 aws-java-sdk-minimal:1.12.163-315.v2b\_716ec8e4df aws-java-sdk-ssm:1.12.101-300.vc09c7be9cb57 basic-branch-build-strategies:1.3.2 bitbucket:223.vd12f2bca5430 bootstrap4-api:4.6.0-3 bootstrap5-api:5.1.3-1 bouncycastle-api:2.25 branch-api:2.7.0 build-monitor-plugin:1.13+build.202110011223 build-timeout:1.20 caffeine-api:2.9.2-29.v717aac953ff3 checks-api:1.7.2 cloudbees-bitbucket-branch-source:723.vbabdf19eb4c7 cloudbees-folder:6.16 command-launcher:1.6 config-file-provider:3.8.1 copyartifact:1.46.2 credentials:2.6.1 credentials-binding:1.27 discard-old-build:1.05 display-url-api:2.3.5 docker-build-step:2.8 docker-commons:1.17 docker-workflow:1.26 durable-task:493.v195aefbb0ff2 ec2:1.68 echarts-api:5.2.2-1 email-ext:2.84 embeddable-build-status:2.0.3 external-monitor-job:1.7 file-operations:1.11 font-awesome-api:5.15.4-1 generic-webhook-trigger:1.77 git:4.10.0 git-client:3.10.0 git-server:1.10 github:1.34.1 github-api:1.133 github-branch-source:2.11.3 gradle:1.37.1 greenballs:1.15.1 handlebars:3.0.8 handy-uri-templates-2-api:2.1.8-1.0 htmlpublisher:1.28 ivy:2.1 jackson2-api:2.13.0-230.v59243c64b0a5 javadoc:1.6 javax-activation-api:1.2.0-2 javax-mail-api:1.6.2-5 jdk-tool:1.5 jjwt-api:0.11.2-9.c8b45b8bb173 jquery-detached:1.2.1 jquery3-api:3.6.0-2 jsch:0.1.55.2 junit:1.53 kubernetes-cli:1.10.3 kubernetes-client-api:5.4.1 kubernetes-credentials:0.9.0 ldap:2.7 ldapemail:0.8 lockable-resources:2.12 mailer:408.vd726a\_1130320 mapdb-api:1.0.9.0 matrix-auth:2.6.8 matrix-project:1.20 maven-plugin:3.15.1 mercurial:2.15 minio:1.3.0 momentjs:1.1.1 node-iterator-api:1.5.1 nodejs:1.4.1 okhttp-api:4.9.2-20211102 pam-auth:1.6.1 permissive-script-security:0.7 pipeline-aws:1.43 pipeline-build-step:2.15 pipeline-github-lib:1.0 pipeline-graph-analysis:1.11 pipeline-input-step:2.12 pipeline-milestone-step:1.3.2 pipeline-model-api:1.9.2 pipeline-model-definition:1.9.2 pipeline-model-extensions:1.9.2 pipeline-rest-api:2.19 pipeline-stage-step:2.5 pipeline-stage-tags-metadata:1.9.2 pipeline-stage-view:2.19 pipeline-utility-steps:2.10.0 plain-credentials:1.7 plugin-util-api:2.5.1 popper-api:1.16.1-2 popper2-api:2.10.2-1 publish-over:0.22 resource-disposer:0.16 run-condition:1.5 sbt:1.5 scm-api:2.6.5 scmskip:1.0.3 script-security:1.78 simple-theme-plugin:0.7 slack:2.48 snakeyaml-api:1.29.1 snyk-security-scanner:3.2.6 sonar:2.14 ssh:2.6.1 ssh-agent:1.23 ssh-credentials:1.19 ssh-slaves:1.33.0 sshd:3.1.0 structs:1.23 subversion:2.15.1 terraform:1.0.10 timestamper:1.13 token-macro:267.vcdaea6462991 trilead-api:1.0.13 variant:1.4 view-job-filters:2.3 windows-slaves:1.8.1 workflow-aggregator:2.6 workflow-api:2.47 workflow-basic-steps:2.20 workflow-cps:2633.v6baeedc13805 workflow-cps-global-lib:2.21 workflow-durable-task-step:2.35 workflow-job:2.42 workflow-multibranch:2.26 workflow-scm-step:2.13 workflow-step-api:622.vb\_8e7c15b\_c95a\_ workflow-support:3.8 ws-cleanup:0.39 ---
**Author:** ![Fito\_o](https://avatars.discourse-cdn.com/v4/letter/f/f19dbf/32.png) [@Fito\_o](https://community.jenkins.io/u/Fito_o)\ **Post date:** [March 25, 2025, 12:30pm UTC](https://community.jenkins.io/t/problem-with-integration-bitbucket-cloud-and-jenkins-using-bb-workspace-access-token/19121/2 "2025-03-25T12:30:26Z")
I am facing the same problem. We tried using Access Tokens in the same way you mentioned, but without success. We believe Jenkins is incompatible with the use of access tokens in version 2.456. We resorted to using multiple service users within the workspace connected to Jenkins using App passwords as recommended by Atlassian, but we are also hitting the rate limit very quickly. Have you found any solution to this?