2 min read

Connect Bitbucket to EngLedger

Authorise EngLedger with Bitbucket OAuth, choose repositories to sync and understand what's imported, token refresh and rate limits.

Updated 12 July 2026

EngLedger connects to Bitbucket Cloud with OAuth 2.0. You authorise access once; EngLedger stores the tokens securely and refreshes them automatically as they expire.

Authorise Bitbucket

  1. Open Integrations in EngLedger and choose Connect on the Bitbucket card. You're redirected to Bitbucket's authorisation page.

  2. Approve the request. EngLedger creates a connection for each workspace your account can access, then returns you to the repository selection screen.

Choose repositories

As with GitHub, every repository is selected by default after connecting. Deselect what you don't want synced. Each repository has two scopes: Commits & PRs (branches, commits with changed files, pull requests and reviews) and Issues (Bitbucket issues as lightweight tickets). Saving the selection starts the first sync.

What gets synced

Repositories, branches, commits (with changed files), pull requests and reviews from your selected repositories. Commit and PR authors are recorded as provider identities to be linked to people. See People and identities. Ticket references in commit messages, branch names and PR titles (such as a Jira key like ENG-123) create links between code and tickets automatically.

Token refresh and reauthorisation

Bitbucket access tokens are short-lived. EngLedger refreshes them in the background using the refresh token, so day-to-day you shouldn't need to think about it. If the refresh token itself is revoked or invalidated (for example, the authorising user's access changes) the integration is marked Needs reauth on the Integrations page. Reconnecting through the same Connect flow restores it; your repository selection is preserved.

Sync cadence and rate limits

Scheduled sync runs every 30 minutes by default. Bitbucket's API allows 1,000 requests per hour, which is lower than other providers. EngLedger tracks consumption and throttles before hitting the ceiling, deferring work to the next window instead of failing. First-time backfills of large workspaces can therefore take several sync windows to complete; incremental syncs after that are comfortably inside the limit.

Disconnecting

Disconnect pauses the integration; synced data is retained and syncing stops. Reconnect at any time with the same flow.

Next steps