New API option for First-time Edited/Reviewed Words in Activity Reports

1

We’re excited to announce a new enhancement to the Transifex API that brings more granular control to your organization’s reporting. You can now toggle the “First-time Edited/Reviewed Words” logic directly via the API when generating activity reports.

The problem this solves

When measuring team productivity, many organizations need to distinguish between:

  • Total activity: Every time a string is edited or reviewed.

  • Unique progress: Only the very first time a word is edited or reviewed in a specific period.

Previously, while this toggle was available in the Transifex UI, API users received the default report data without an easy way to isolate “first-time” actions. This made it difficult to automate reporting that matches the specific “unique work” views used by project managers in the dashboard.

What’s new

We have introduced a new boolean field, first_time_edits, to the Organization Activity Report download endpoint. This allows you to programmatically define whether the report should count every action or only the initial edit/review for each string.

How it works

When triggering a new report via the API, you can now include the first_time_edits attribute in your request body.

Endpoint: POST https://rest.api.transifex.com/organization_activity_reports_async_downloads

Request Body Example:

JSON

{
  "data": {
    "attributes": {
      "date_from": "2025-10-01",
      "date_to": "2025-10-31",
      "first_time_edits": true
    },
    "type": "organization_activity_reports_async_downloads"
  }
}

  • first_time_edits: true: The report will only count the first time a user edited or reviewed a string during the selected period.

  • first_time_edits: false (Default): The report will include all edits and review actions.

What this enables

  • Accurate Automation: Ensure your automated billing or productivity scripts match the exact “First-time” filters used in the Transifex UI.

  • Better Data Insights: Easily isolate unique contributions versus repetitive edits when analyzing vendor or translator performance.

  • Streamlined Reporting: No more manual data cleaning to remove duplicate actions on the same strings.

Check out the full technical details in our API Documentation.

Let us know how this helps your reporting workflow or if you have any questions!

1 Like