Two-Legged Token Lifecycle
A 3-step recipe with Autodesk. We can help you get access.
Recipe · 3 steps
Two-Legged Token Lifecycle
with Autodesk
Obtain, introspect, and revoke a two-legged APS access token.
- Request an access token with the client_credentials grant. Two-legged tokens represent the application itself, not an end user.
- Introspect the freshly minted token to confirm it is active and to read back the scopes and expiry the authorization server actually granted, which may be narrower than what was requested.
- Revoke the access token once the work is complete so it cannot be reused if it leaks from logs or a crash dump.
What you'll need to have ready
- clientId: The Client ID of your APS application.
- clientSecret: The Client Secret of your APS application.
- scope: Space-separated list of scopes to request (e.g. "data:read data:write bucket:create").
For your developer
Arazzo workflow autodesk:two-legged-token-lifecycle, 3 operations: getToken → introspectToken → revokeToken. Specs on APIs.io.