AIP-103: Add Core API endpoints for task state and asset state

[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

closes:

Proposed change

Adds public REST endpoints for task state and asset state under /api/v2.

Task State — scoped to a task instance within a DAG run:

GET /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/state
GET /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/state/{key}
PUT /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/state/{key}
DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/state/{key}
DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/state

map_index query param (default -1). ?all_map_indices=true on the clear endpoint wipes state across all mapped instances of the task.

Asset State — cross-run, scoped to an asset:

GET /api/v2/assets/{asset_id}/state
GET /api/v2/assets/{asset_id}/state/{key}
PUT /api/v2/assets/{asset_id}/state/{key}
DELETE /api/v2/assets/{asset_id}/state/{key}
DELETE /api/v2/assets/{asset_id}/state

URL patterns follow existing conventions — task state mirrors XCom, asset state mirrors /assets/{asset_id}/.

Testing

Task State APIs

1. set API

2. List API

3. get API

4. delete API

5. clear API

For this first add couple of task states for mapped task

Without all_map_indices flag (only current deleted)

With the all_map_indices flag:

Asset State APIs

Using id=4 to test

1. set API

2. get API

3. list API

4. delete API

5. To test clear, will add a few asset states

All clear!

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[jason810496]

Nice! LGTM overall, thanks. There're same questions for the task state endpoint.

[pierrejeambrun]

Small nits. Looking good overall

[amoghrajesh]

The failing tests in https://github.com/apache/airflow/actions/runs/26144521163/job/76898272728?pr=67041, seem to be unrelated to these changes.

[amoghrajesh]

Merging this one in, thanks for reviews!

[github-actions]

Backport failed to create: airflow-ctl/v0-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	airflow-ctl/v0-1-test

You can attempt to backport this manually by running:

cherry_picker f9e4e6e airflow-ctl/v0-1-test

This should apply the commit to the airflow-ctl/v0-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[kaxil]

The failing tests in https://github.com/apache/airflow/actions/runs/26144521163/job/76898272728?pr=67041, seem to be unrelated to these changes.

Do you think it was because of PR behind main. Or trying to think why langchain wasn't installed

[amoghrajesh]

@kaxil it was an actual issue fixed via #67237