Dependency type (FS / FF / SS / SF) should be provided by the API

English Forum Developers & API
1

Hi,
the type of a dependency (FinishToFinish, FinishToStart, …) is one of the fundamentals of project management.
It is considered by Asana (even with great automatic date shifting!) but not by its API. Knowing only about “Blocking” or “BlockedBy” is almost meaningless, it is mandatory to know the associated constraint type (FS / FF / SS / SF).
In my case I use the API to run some specific analyses on our project plans, which I cant get done directly by Asana (e.g. via dashboard). But my analyses are useless without knowing the dependency constraints.
Hence please extend the API (https://app.asana.com/api/1.0/tasks/{task_gid}/dependencies) to access this information!
Thanks,
Erik.

2

Welcome, @Erik_Labadie, and thanks for adding this. Don’t forget to click the title to scroll to the top and vote by clicking the Vote button; that’s the quickest and most effective way to express your support for a request.

@Phil_Seeman, perhaps you want to tag a dev contact since this is not in the otherwise monitored English Forum > Developers & API?

Thanks,

Larry

3

I did move this to the English Forum > Developers & API forum section as that’s where the Asana devs prefer.

Yes, I asked for this capability right when multiple dependency types were released. It’s not on the roadmap that I’ve heard, but @John_Baldo @Andrew-asana here is another request for it, including a use case.

4

Thank you. I’ve routed this feedback to the right place. Will follow up with any updates.

7

Hello Asana Community,

I wanted to raise a general observation regarding task dependency relationships and automation in Asana.

While Asana supports dependencies between tasks, the specific dependency relationship types-such as Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF)—are not exposed via the public Asana API.

As a result:

  • When building automations using Script Actions, the Asana API, or external platforms,

  • It’s not possible to determine the exact relationship type between two dependent tasks,

  • Which makes it difficult (or impossible) to accurately automate date shifting or schedule recalculation in a way that mirrors native UI behavior or traditional project-management tools.

This limitation affects general automation scenarios, especially for teams attempting to:

  • Automate duration-based scheduling

  • Programmatically maintain dependencies

The dependency data returned by the API allows identifying which tasks are related, but not how they are related (i.e., the dependency type), which restricts automation logic to assumptions rather than explicit rules.

8

Hi @Rithika_Pujary,

I’ve merged your post with an existing topic for this request (which I fully support!).