Wrike API Documentation- Dependencies

Hi Timothy Livingston, thank you for your feedback. Milestones do not have start dates, it's possible to set only their due dates. That's why the Dependencies API query supports only Finish to Finish dependency with milestones. The same is true when you create dependencies via workspace. As for cases when a call accidentally duplicates the existing dependency, it is expected that an error will be displayed since the dependency itself already exists.

I agree that having these cases documented in the Developers portal might help users identify the root cause of the error message and correct their API queries. Our developers will review your suggestion. Thank you for bringing this to our attention🙌

Lisa K. Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa K. Wrike Team member Become a Wrike expert with Wrike Discover

Here is a response I received from the Wrike support team via email:

I am afraid it might be really tricky to get a comprehensive list of conditions that may cause error 403 when creating dependencies via API. Essentially, it would be basically anything that would forbid you to do the same in the Workspace manually, such as:

• You cannot add an FS dependency to a milestone task because milestones do not have a start date, hence the error.
• You cannot add a dependency between tasks when there is one of the same type already between these tasks.
• You cannot add a dependency if adding one would create a loop (in the most simple case, it is like if there is an FS dependency from task 1 to task 2, you cannot add an FS dependency from task 2 to task 1). 
• You cannot add a dependency if the user that authorised the API does not have permissions to create dependency at all or in this particular folder due to their license or job role limitations

The above seems to cover the majority of the scenarios. 

I am afraid, our API does not provide more detailed information about a specific reason for 403 error. I will add the suggestion to the backlog of the team that is responsible for API.

The only problem I have now is identifying if the dependency was not created because it already existed (this is OK for my program), or if there was another reason it wasnt created (which is bad for my program). I don't believe there is currently a way to tell. I suppose I will need to query for a similar dependency to check if it already exists!

Hello Timothy Livingston, I see that you're in touch with our Support agents about your query. Please let me know if you have any other questions 🙋🏻‍♀️

Yes I have been in contact with support. Thanks Cansu. 

Also adding here for sake of completeness- It is currently not possible to add Lead/Lag times to dependencies via the API.

For Example, the following dependency is allowable through the Wrike UI: "23FS +2d". However the "+2d" portion is not yet possible via the API.

Thanks for updating the thread Timothy Livingston 👍🏼