ACC Admin added a new API enhancement to retrieve all projects associated with a specific user one month ago at https://aps.autodesk.com/blog/acc-admin-api-new-api-list-all-projects-specified-user. Today, we continuously enhanced our ACC Admin API to support retrieve more information including products and roles for a specific user, here are details:
What's New?
- Retrieve all products associated with a specific user: GET accounts/{accountId}/users/{userId}/products
- Retrieve all roles associated with a specific user: GET accounts/{accountId}/users/{userId}/roles
Key Highlights
- Supports both ACC and BIM 360 projects
- Flexible filtering options to fine-tune your queries
- For any product or role returned for the user, the object also list all the projects(by projectIds) which the product or role is active in, take GET accounts/{accountId}/users/{userId}/roles for example as follow, you can see the project list where this user role is involved.
{
"pagination": {
"limit": 5,
"offset": 0,
"totalResults": 1
},
"results": [
{
"id": "4e7b02ae-2994-4210-9153-84bfa9a23a63",
"status": "active",
"name": "BIM Manager",
"key": "bim_manager",
"createdAt": "2021-02-06T21:29:46.026Z",
"updatedAt": "2021-02-06T21:29:46.026Z",
"projectIds": [
"4ea4c4ac-ae11-4ccb-9386-aa84adab4306",
"47ed4856-7853-40ee-b69d-5b27c7d6dcb7",
"dd066171-1ed0-41d5-94d2-07c8c636bcb8",
"011cb139-3c3f-4c2f-b265-922a9484580c",
"5bc35696-b686-4589-8ab0-b9c108de9a4c",
"6c882c74-a8e8-488f-8a0e-7a4c840c444e"
]
}
]
}Important Notes
This API involves two types of user IDs:
-
User-Id(Header parameter): This represents the user on whose behalf the request is being made.- Must be an Account Admin
- Not needed for 3-legged OAuth
- For 2-legged OAuth, it's optional, required if you want to specify an admin user, but you can also ignore this if don't want to specify an admin user.
-
userId(URI parameter): This is the ID of the user whose information(products/roles) you want to retrieve.
Supports Secure Service Accounts
If you are using SSA (Secure Service Accounts), make sure you do the following:
- Using SSA token as 3LO, the SSA user must have Account Admin permission.
- The SSA token must have account:read scope.
- You can check the products/roles that the SSA user is involved in. Use the `
serviceAccountId`as in the URI parameter of userId.
