Feature Request: Threaded comment replies in the API

Asana Community API & Developers
1

Threaded Comments went live in the Asana web and mobile apps on September 11, 2026 (announcement). The API has no support for them yet. This request asks for API support to read and create replies.

Current API behavior

We checked the API reference and the OpenAPI spec (Asana/openapi, build of 2026-10-14):

  • POST /tasks/{task_gid}/stories accepts text, html_text, is_pinned, and sticker_name. No field specifies the comment that a new comment replies to.
  • The story schema has no field for a parent comment, a thread, or a reply count.
  • The spec does not mention replies or threads anywhere.

An earlier staff answer said that Asana had no concept of comment threading, in the API or in the UI. The UI part changed with the September launch. In the launch thread, a question about API support is still unanswered.

Use case

We run an AI agent that works on Asana tasks. The agent posts progress updates and approval requests as task comments through the API. Team members answer those comments in Asana.

With threading available, team members can reply in the thread of the comment they answer. When they do, two problems follow:

  1. The agent cannot tell which comment a reply answers. A task often has many agent comments. A reply such as “Approved” does not say which one it approves.
  2. The agent cannot reply in a thread. Its answers appear as new top-level comments. One conversation then splits into separate places in the task.

Requested changes

The field names below are suggestions.

  1. Read: Add a reply_to field (compact story, null for top-level comments) to comment stories. A num_replies field would also help.
  2. Write: Accept reply_to (a story gid) on POST /tasks/{task_gid}/stories to create a reply. Support the same field on other objects that have threaded comments, such as goals.
  3. Webhooks: Include the replied-to story in story added events. The existing parent field of an event already refers to the task, so a separate field avoids confusion.

Questions

  1. Is API support for threaded comments on the roadmap?
  2. Do replies appear in GET /tasks/{task_gid}/stories today, as ordinary comment_added stories? A community report suggests that they do. If so, integrations can at least read every reply until a parent field exists.
  3. The story schema has a story field that is documented only as “Conditional”. Does it point to the parent comment for replies? If so, please document it.
1 Like