# 🚀 Enhancement: Reporting on Strings included in tasks via the Tasks API

**URL:** <https://community.transifex.com/t/enhancement-reporting-on-strings-included-in-tasks-via-the-tasks-api/5096>\
**Category:** What's new?\
**Tags:** api\
**Created:** [December 19, 2025, 7:52am UTC](https://community.transifex.com/t/enhancement-reporting-on-strings-included-in-tasks-via-the-tasks-api/5096 "2025-12-19T07:52:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maria](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/maria/32/1132_2.png) [@maria](https://community.transifex.com/u/maria)\
**Post date:** [December 19, 2025, 7:52am UTC](https://community.transifex.com/t/enhancement-reporting-on-strings-included-in-tasks-via-the-tasks-api/5096/1 "2025-12-19T07:52:54Z")

</div>

We’re excited to announce a new enhancement to the Transifex API that makes it possible to report on **source strings included in tasks** , while also understanding their **translation status** and whether a related task is **open**.

### 🔍 The problem this solves

Many teams want to answer questions such as:

- _Which strings in our code are missing translations?_

- _Are those strings already included in a task?_

- _If so, what is the status of that task?_

Previously, there was no straightforward way to determine **which strings belong to which tasks** using the API, making it difficult to correlate missing translations with task coverage.

### ✨ What’s new

With this enhancement, you can now connect **tasks to their underlying source strings** , enabling accurate reporting and automation around task-based localization workflows.

### 🔄 How it works

Here are the core API endpoints involved in this flow:

1. **List tasks**

2. **List task languages**

3. **Get a Resource Translations collection**

> Note: You can also combine filters such as `filter[resource]`, `filter[language]`, or others depending on your use case. If there is no translation in the response, the string is considered untranslated.

### 📊 What this enables

- Reporting on strings included in tasks at the source-string level

- Identifying missing translations and whether they’re already covered by an open task

- Tracking task coverage and translation progress more accurately

- Building better dashboards, audits, and automation around localization

This enhancement closes the gap between **tasks and strings** , giving you the visibility needed to manage translation work more effectively. Let us know how you’re using it or if you have feedback!