For Developers
Build Localization Into the
Stack You Already Run
Wordbee exposes the whole platform as an API. Projects, jobs, segments, suppliers, and invoices are reachable from your own code; webhooks fire when status changes; and connectors round-trip content from Git and your CMS. Localization runs alongside your deploys, not as a manual step between them.
The Solution
Localization That Runs From Your Pipeline
Wordbee exposes the platform as an API, so content moves in and out from your own code, with no export, email, re-importing, or re-keying. Strings stream in, apply translation memory, route on their own, and come back to the source confirmed, on the same release cadence as the rest of your build.
- Push and pull from your own code, instead of export, email, and re-import
- Content streams in through the API, applies translation memory, and routes on its own
- Confirmed translations flow straight back to the source
- A webhook fires on status changes, so your systems react without polling
- Jobs auto-created
- TM leverage + MT
- Routed, QA’d, returned
System API · v1 and v2
One API Across the Whole Object Model
The REST API reaches nearly every object in Wordbee. Retrieve and manipulate the records your integration needs, authenticated by a key tied to a specific user's access rights.
Projects, Jobs & Workflows
Create projects, count words, assign jobs, and track status through every workflow step, then download deliverables.
Read moreSegments & Memories
Read and write segments, and search and export translation memories and termbases.
Read moreClients & Suppliers
Manage the client and supplier records that work is quoted to and routed to.
Read moreInvoices & Finance
Create and manage invoices and line items, so billing systems read straight from Wordbee.
Read moreTwo Versions, v1 and v2
v2 is the modern, actively developed API with user-based auth and broad coverage; v1 is still maintained. Use v2 for new work.
Read moreKeys Tied to a Login
Each API key inherits a specific user’s access rights, with short-lived tokens on requests. Enable or revoke per user.
Read moreEvents & Continuous Content
Webhooks Push Status, the Flex API Pushes Strings
Webhooks fire when a project changes status, so your CI build, CRM, chat, or publishing step reacts the moment work moves, with no polling. For content itself, the Flex API streams strings in and out continuously: .wbflex containers carry new and changed strings into Wordbee with branches and versioning, and pull the latest translations back, so a feature branch and a release branch each keep their own localization state.
- Webhooks fire on project status changes
- Drive CI/CD builds, CRM updates, chat alerts, and publishing
- The Flex API (.wbflex containers) pushes and pulls strings continuously
- Branch and version support, so each branch keeps its own state
- Only new and changed strings move, with translation memory applied automatically
workflow
Git & Build Pipelines
A Free Git Connector, Built for CI/CD
Beebox is the middleware that connects repos and content systems to Wordbee. The Git connector is free, branch-based, and handles many branches at once; hot folders and a Web API wire it into your build pipeline.
Free Git Connector
Connect GitHub, GitLab, Bitbucket, or SVN. The Git connector ships free with Beebox.
Read moreBranch-Based, Multi-Branch
Localization tracks your branches: a release branch and a feature branch each keep their own translation state.
Read moreHot Folders & IN/OUT
Drop source into an IN directory and collect translations from OUT, a file-based flow that needs no integration code.
Read moreWeb API & Webhooks
Trigger runs and react to them from your build pipeline through Beebox’s Web API and webhooks.
Read moreOnly What Changed
Beebox extracts only new and modified segments since the last run, and applies translation memory before MT.
Read moreCMS & Storage Too
Beyond Git: AEM, Sitecore, SharePoint, Drupal, WordPress, and cloud storage through the same middleware.
Read moreWhy Developers Choose Wordbee
It Connects to the Stack You Already Run
No new workflow to adopt, no strings re-keyed by hand.
- Reaches the whole object model: projects, jobs, segments, suppliers, clients, invoices, and memories
- REST API v1 and v2, with keys scoped to a user’s access rights
- Webhooks on status changes drive your CI, CRM, chat, and publishing
- The Flex API pushes and pulls strings continuously, with branches and versioning
- Free, branch-based Git connector for GitHub, GitLab, Bitbucket, and SVN
- Code, resource, and content formats, from JSON and RESX to HTML and InDesign
- Translation memory applied automatically, so repeated content is never re-keyed or re-paid
Common Questions
What Developers Ask Us
Start Building With Wordbee
Start a free trial and read the API docs, or book a working session with an integration engineer to map the API, webhooks, the Flex API, and the Git connector to your pipeline.