Orchestrate your localization workflow with On-demand Fill-ups via API

What's new?
, , ,
1

Orchestrate your localization workflow with On-demand Fill-ups via API

Tired of waiting for “automatic” triggers to catch up with your specific deployment steps?

While Transifex automation is powerful, we know that complex enterprise workflows often require a specific sequence of events—like uploading existing translations or cleaning up legacy strings—before you want the “Auto-Fill” to kick in.

That’s why we’ve introduced On-demand TM, MT, and AI Fill-ups via API. This update gives you granular, programmatic control over exactly when and how automation runs for specific resources and languages.

What’s new?

Trigger automation on your own terms

Previously, fill-ups were tied to project-level “on-upload” toggles. Now, you can keep those global toggles off and use the API to trigger fill-ups exactly when your pipeline is ready.

Instead of a “one-size-fits-all” approach, you can now:

  • Target specific resources: Run a fill-up on one specific file without affecting the rest of the project.
  • Target specific languages: Need to push French live immediately but wait on Japanese? Now you can trigger them independently.
  • Sequential Orchestration:
    1. Upload source content.
    2. Upload existing translations from an external source.
    3. Trigger TM Fill-up via API to fill remaining 100% matches.
    4. Trigger MT or AI Fill-up via API to handle the rest.

Why this matters

This feature is a game-changer for teams using the Transifex API to manage continuous localization:

  • Eliminate Race Conditions: No more worrying if the TM fill-up ran before your “existing translations” upload finished. You control the clock.
  • Granular Logic: Choose whether to run TM, AI, or MT (or all three) in a single call, or keep them separate to allow for human review steps in between.
  • Cleaner TM: Because you control the trigger, you ensure that only the most relevant content is being leveraged at the right time.

How it works

To use this new functionality, ensure that automated fill-ups are disabled in your Project Workflow settings. This prevents accidental triggers and hands the “steering wheel” over to your API calls.

From there, you can send a POST request to the resource_translations_async_fillups endpoint with your desired parameters:

  • translation_memory_fillup: true/false
  • machine_translation_fillup: true/false
  • ai_fillup: true/false
  • Custom options: Set your own fuzzy match thresholds or auto-review policies directly in the payload.

Pro Tip:

Use this to create a “Translation Warm-up” script. Every time a developer pushes a new feature branch, your script can automatically trigger a TM fill-up and an AI translation for just that branch’s resource, ensuring the UI is never empty for your global testers.

Conclusion

By moving from a project-wide toggle to a targeted API execution, Transifex gives developers and localization managers the precision needed for high-scale, complex environments. You stay in control of the workflow, the quality, and the timing.

Check out the full technical details in our Developer Hub and let us know how you’re planning to orchestrate your new automated pipelines!