BeLazy is API-first. Not in the sense that every screen has an endpoint (that would not be useful), but in the sense that localization operations need a simple way to extend any tool, and the BeLazy API is that simple way.
Documentation, refreshed
Our API documentation now lives at api.belazy.cat and is organized around the four main API use cases:
- Project Ingestion: feeding a CMS or an internal request portal into TMS and BMS.
- BMS Integration: integrating BeLazy as the TMS and connector layer with your own business management system.
- BMS Extensions: programmatic, simple access to Plunet, XTRF, or Protemos data through a unified interface.
- AI Workflow: XLIFF-based, TMS-independent toolbox to incorporate automatic text processing steps.
It is the reference whether you are an enterprise team plugging Contentful or your home-grown PIM into translation, implementing TMS-independent AI workflows, you are an LSP building email parsers, or you just want to see the status of your Plunet projects from Make.com, n8n, or another orchestrator.
What is new in this release
- Source files per pricing item. The Create opportunity from workspace call, BeLazy’s main project-creation API, now accepts a source file on each pricing item rather than only at the opportunity level. Different files for different languages can be combined into a single API call. Useful when you ship locale-specific source content.
- Vendor assignments in the BMS Extension API. The BMS Extension API returns full Plunet, XTRF, and Protemos project details for BeLazy-managed projects. It now also returns the assigned vendors. Useful for executive reporting, BI dashboards, and procurement reviews.
- Webhook filtering by connection. Restrict webhook sending to specific connections. If you orchestrate with Make.com or a similar tool, this means fewer scenario runs and decreased costs.
Why this matters
BeLazy’s API is the layer that lets your company’s custom interface, its CMS integration, or its AI agent talk to every TMS, BMS, and vendor portal in the localization stack without writing one integration per system. As the TMS market consolidates, this is the durability layer between your content and your language vendors.
