Skip to main content
Every change made to a translation in Entri is recorded automatically. Version history gives you a complete audit of what a translation looked like at any point in time, who changed it, and when — with the ability to revert to any prior version in one click.

What Gets Recorded

A new version is created whenever a translation value is saved. Each version record includes:
  • The full translation text at that point in time
  • The user who made the change
  • The timestamp of the change
  • The translation status at the time (Untranslated, Translated, Reviewed, or Approved)
History is tracked per key per language. Viewing history for the French translation of button.save shows only changes to that specific key/language pair.

Viewing History

1

Open a key in the editor

Click any key in the translation editor to expand the detail panel.
2

Open Version History

Select the History tab in the key detail panel. The full list of versions appears in reverse chronological order, with the most recent change at the top.
3

Browse versions

Each entry in the list shows the translation text, the author’s name, and the relative timestamp (for example, “3 days ago”). Click any entry to expand it and see the full translation value.

Reverting to a Previous Version

If a translation was changed incorrectly — or if you need to undo an AI-generated translation that wasn’t quite right — you can restore any previous version.
1

Find the version you want to restore

Open the History tab and locate the version you want to go back to.
2

Click Revert

Click the Revert button on that version entry. Entri immediately sets the translation value back to that version’s text.
3

Confirm

The revert itself creates a new version entry in the history, so the revert action is also tracked. You can always undo a revert by reverting again.
Reverting does not delete any history. Every state the translation has ever been in remains in the history log.

Via API

You can retrieve version history and trigger reverts programmatically.
# Get the version history for a key/language pair
GET /api/projects/{projectId}/keys/{keyId}/translations/{language}/history

# Revert to a specific version
POST /api/projects/{projectId}/keys/{keyId}/translations/{language}/revert
The revert endpoint accepts a version ID from the history response. The API is useful for automated quality checks or tooling that needs to roll back translations in bulk.

When to Use Version History

  • After a bad AI batch translation — quickly restore the previous approved values
  • Investigating a regression — find out when and why a string changed
  • Auditing translator work — see who changed what and when across the project
  • Restoring accidentally overwritten translations — recover values that were overwritten during an import with overwrite=true