Main site
Localit Docs
Getting started
IntroductionCreating Your First ProjectSetting Up Your TeamBasic Localization Workflow
File Formats
File Formats OverviewJSON Format GuideXML (Android) Format GuideiOS .strings Format GuideiOS .stringsdict Format Guide (iOS Plurals)PO/POT/MO (Gettext) Format GuideSRT Subtitles Format Guide
Import & Export
File Upload Settings ConfigurationUniversal PlaceholdersFile Download Settings ConfigurationWorking with Plural Forms
Integrations
GitHub Integration - Complete Setup GuideGitLab Integration - Complete Setup GuideBitBucket Integration - Complete Setup Guide
Team Management
Roles and Access RightsTeam ManagementTeam ChatComments - Translation DiscussionLogs and Change History
Translation & Localization
Translation and Review ModeAI Translations and OrdersQuality Control - Status ManagementPlurals and Arrays in Translation EditorUniversal Placeholders in Translation Editor
FAQ
Frequently Asked Questions (FAQ)

BitBucket Integration - Complete Setup Guide

Ilya Donder

Localit.io provides powerful BitBucket integration, allowing you to automate localization workflow and synchronize translations directly with your repository.

Initial integration setup

Step 1: Access settings

  1. Open your project in Localit.io

  2. Go to the "Integrations" section

  3. Select BitBucket from the list of available services

263

Step 2: Creating Access Token

BitBucket uses Personal Access Token for API access authentication.

Step 1: Navigate to Repository settings

264

  1. Open the repository for which you need to create an integration.

  2. Go to the Repository settings.

  3. Select Access Token.

Step 2: Create new token

265

  1. Click "Create access token"

  2. Fill in basic token information

Step 3: Configure basic parameters

266

  • Label: Localit.io Integration

Step 4: Configure permissions

Required permissions:

Repositories:

  • Read: Purpose: Reading repository content | Needed for: Loading localization files

  • Write: Purpose: Writing to repository | Needed for: Sending translations back to repository

Pull requests:

  • Read: Purpose: Reading pull request information | Needed for: Integration workflow management

  • Write: Purpose: Creating and managing pull requests | Needed for: Automated translation updates

Webhooks:

  • Read and write: Purpose: Webhook management | Needed for: Automatic synchronization on changes

Step 5: Create and copy token

269

  1. Click "Create"

  2. Important: Copy the token immediately — it won't be shown again

  3. Save the token in a secure location

Configuring connection parameters in Localit.io

Step 1: Enter token

271

  1. Return to Localit.io interface

  2. Paste the copied token into "Personal access token" field

  3. System automatically validates the token

Step 2: Enter workspace

273

Step 3: Select repository

280

  1. Choose target repository from dropdown list

  2. Search by name available for convenience

  3. Only accessible repositories are displayed

Step 4: Specify working branch

  1. Specify working branch (usually main, master, or develop)

  2. Search by branch name available

  3. System shows all available branches

275

Platform and file configuration

Step 1: Choose platform type

276

Select platform type according to your project:

  • Web (.json, .po, .pot, .mo)

  • Android (.xml)

  • iOS (.strings, .stringsdict)

  • Other (.srt, custom formats)

Step 2: Add files

  1. Click "Next" to proceed to file selection

  2. Click "Add file"

  3. Select needed files in repository file tree

277

Step 3: Configure languages

278

  1. Specify corresponding language for each file

  2. System automatically detects language by file path

  3. Correct automatic detection if needed

Step 4: Save configuration

279

  1. Review all settings

  2. Click "Save"

  3. Integration will be configured and ready to use

Initial localization setup

Important for new projects

If you haven't translated your project to other languages yet, follow this workflow:

Step 1: Create empty localization files

Create empty localization files in your BitBucket repository. Follow folder structure for your platform:

For iOS:

en.lproj/Localizable.strings
es.lproj/Localizable.strings  
fr.lproj/Localizable.strings

For Android:

app/src/main/res/values/strings.xml
app/src/main/res/values-es/strings.xml
app/src/main/res/values-fr/strings.xml

For Web:

src/locales/en.json
src/locales/es.json
src/locales/fr.json

Step 2: Connect integration

281

  1. Set up BitBucket integration as described above

  2. Connect created files to project

  3. Perform initial Pull to load structure

Step 3: Translate keys

285

  1. Translate necessary keys using translation editor

  2. Or order automatic translation through AI services

  3. Review translation quality

Step 4: Send to BitBucket

282

  1. Perform Push to send translations to repository

  2. Verify files updated in BitBucket

  3. Test localization in application

Pull requests (Import from BitBucket)

Initiating Pull request

283

  1. Go to project "Integrations" section

  2. Find connected BitBucket repository

  3. Click "Pull" button

Within seconds project will be updated - all keys from BitBucket will be loaded into your Localit.io project

Parameter configuration: Pull request parameters correspond to manual file upload parameters. Details in File Upload Guide.

Automatic synchronization with BitBucket

  • Function: Project automatically updates when repository changes

  • Requirements: Webhook permission when creating token

  • Benefits: Continuous synchronization without manual intervention

Push requests (Export to BitBucket)

Initiating Push request

  1. Go to project "Integrations" section

  2. Find connected BitBucket repository

  3. Click "Push" button

  4. Within seconds repository will be updated - all translations from Localit.io will be sent to your BitBucket repository

Parameter configuration: Push request parameters correspond to manual file download parameters. Details in File Download Guide.

Troubleshooting

Token issues

Token not working:

  • Check token expiration date in BitBucket Settings

  • Ensure correct copying (no extra spaces)

  • Verify token permissions

Insufficient permissions:

  • Return to token settings in BitBucket

  • Add missing permissions (Repositories: Read/Write, Pull requests: Read/Write, Webhooks: Read/Write)

  • Recreate token if necessary

Repository issues

Repository not displayed:

  • Ensure token has repository access

  • Check that repository is not archived

  • For private repositories ensure appropriate permissions

Files not synchronizing:

  • Check correct file path specification

  • Ensure files exist in specified branch

  • Verify file format matches expected

Webhook issues

Automatic synchronization not working:

  • Check webhook settings in BitBucket repository

  • Ensure token has webhook permissions

  • Verify webhooks not blocked by firewall

284

Best practices

Token security

Recommendations:

  • Set minimal necessary permissions

  • Regularly update tokens

  • Remove unused tokens

  • Monitor token usage

Workflow organization

Branch strategy:

  • Use separate branch for localization

  • Configure automatic merge to main branch

  • Regularly synchronize changes

Change monitoring:

  • Set up Pull/Push operation notifications

  • Regularly check synchronization status

  • Maintain change logs for audit

GitLab Integration - Complete Setup Guide
Complete GitLab integration guide for Localit.io TMS. Learn Project Access Tokens, webhook automation, self-hosted GitLab support. Automate localization workflow with pull/push synchronization, automatic translation updates, and secure repository access.
In this article