API Authentication
Understanding Access Tokens
Every request to the Fusion Operations API must carry an access token. This token tells the Fusion Operations service whether the requester is authorized to execute the requested operation.
Fusion Operations API only supports three-legged access tokens (user-level tokens).
Three-Legged OAuth
When an app needs to access resources belonging to an end user, that user must explicitly provide authorization. The typical mechanism, in the case of a web app, is for the app to redirect the user to an Autodesk login page with information about which of the user’s resources it wishes to access. The user then provides explicit consent, letting APS know that the referring app is to be granted the requested access. The user is then redirected back to the app, which can then access the required resources. This kind of flow is called “three-legged” because your app, APS, and the end user make up the three “legs” of the flow. Three-legged authentication can be done by using authorization code. When the authorization code grant is used, an Authorization Code is issued to the user to exchange it to obtain Access Token and Refresh Token.
You should follow the instructions of the following link to obtain your access token: Generate a three-legged token.
Connect APS App with Fusion Operations
A single Autodesk account can be linked to multiple Fusion Operations accounts. So, we need to link the APS App to the Fusion Operations account. This link is done through the clientId. The list of Apps connected to my Fusion Operations account can be consulted here. To create a new integration between the App and the Fusion Operations account the user can access this page, fill the Name with a integration name and the clientId with the APS generated id.
Scopes
A scope is a permission that is set on a token, a context in which that token may act. For example, a token with the data:read scope is permitted to read data within the Fusion Operations API and can be used on those endpoints that require that scope. Tokens without that scope would be denied access to such endpoints.
| Scope | HTTP Methods allowed | Description |
|---|---|---|
| data:read | GET | Allows to retrieve data. Using filters or directly using entity Id. |
| data:write | POST, PATCH, DELETE | Allows to manipulate data. Change, create or delete entities are permitted. Read permissions allowed too. |