|
Documentation
Book a DemoPlatform
PlatformMCPCLIAPIWorkflows
GuidesChangelog
All releases

W12 – One POST, every locale: the async localization API ships

Max PrilutskiyMax Prilutskiy, CEO & Co-Founder·Published about 2 months ago·1 min read

You can now fan out a single localization request across every target locale in one POST and pick the results up via webhook. Before this week, the only path was the synchronous endpoint – which meant either holding a request open for minutes on long content, or building your own queue. The async localization API is that queue, hosted: source payload in, job IDs out, webhook fires per locale as each finishes. It's also the foundation for the localization pipeline that follows in later weeks.

Also shipped#

  • Glossary CSV upload. Bulk-import glossary items from CSV with conflict resolution on collision, so re-imports don't duplicate entries.
  • Async API now accepts nested objects and arrays. Source payloads aren't restricted to flat key-value records anymore.
  • Logs page renders orders of magnitude faster. inputData and outputData removed from the list endpoint (still available on detail), so the table doesn't ship every payload to render a row.
  • Jira and GitHub now connect over OAuth. Both integrations switched off API-token setup.
  • Jobs UI first surface for the async API. Inspect job groups and per-locale status from the dashboard.