Retiring BIM 360 Issues (v1) Endpoints

Does your application use BIM 360 Issues (v1) API? If so, please read on.  

Autodesk plans to retire eleven (11) BIM 360 Issues (v1) API endpoints. Issues API is a shared component across BIM 360 and is used by different modules. Issues in BIM 360 is one of the first functionalities included when BIM 360 Docs was first introduced. Since then, the functionality was extended and adapted by other services. Recently we have released the version 2 of BIM 360 Issues API. For more information about the Issues (v2) API, please take a look at this blog post. 

This plan for retirement applies to BIM 360 only. Autodesk Construction Cloud (ACC) unified products. are not affected. 

Action Required

If you are using the following eleven (11) Issues (v1) API endpoints with BIM 360, please migrate to Issues (v2) API by July 5th, 2023, at which point the Issues (v1) API endpoints will be deprecated and stop functioning. Failure to migrate in a timely manner will result in breaking the workflow in your application.

BIM 360 Issues (v1) API (retiring):  

• GET users/me
• GET issues
• GET issues/:id
• POST issues 
• PATCH issues/:id
• GET issues/:id/comments
• POST issues/comments
• GET issues/attachments
• POST issues/attachments
• GET root-causes
• GET ng-issue-types

Replace with:  

BIM 360 Issues (v2) API (replacement):  

• GET users/me
• GET issues
• GET issues/:issueId
• POST issues 
• PATCH issues/:issueId
• GET comments
• POST comments
• GET attachments
• POST attachments
• GET issue-root-cause-categories
• GET issue-types

You can find more detailed information on BIM 360 Issues API (v1) to (v2) migration guide here:

• BIM 360 Issues (v1) to (v2) Migration Guide 

If you encounter any issues or have any questions about this migration, please contact aps.help@autodesk.com