{ "opencollection": "1.0.0", "info": { "name": "Construction.Account.Admin Account Management Token API", "version": "1.0" }, "request": { "auth": { "type": "oauth2", "flow": "client_credentials", "accessTokenUrl": "", "credentials": { "clientId": "{{clientId}}", "clientSecret": "{{clientSecret}}" } } }, "items": [ { "info": { "name": "Token", "type": "folder" }, "items": [ { "info": { "name": "Authorize User", "type": "http" }, "http": { "method": "GET", "url": "https://developer.api.autodesk.com/authentication/v2/authorize", "params": [ { "name": "client_id", "value": "", "type": "query", "description": "The Client ID of the calling application, as registered with APS." }, { "name": "response_type", "value": "", "type": "query", "description": "The type of response you want to receive. Possible values are: \n\n- ``code`` - Authorization code grant.\n- ``id_token`` - OpenID Connect ID token.\n" }, { "name": "redirect_uri", "value": "", "type": "query", "description": "The URI that APS redirects users to after they grant or deny access permission to the application. Must match the Callback URL for the application as registered with APS.\n\nMust be specified as a URL-safe string. It can include query parameters or any other valid URL construct.\n" }, { "name": "nonce", "value": "", "type": "query", "description": "A random string that is sent with the request. APS passes back the same string to you so that you can verify whether you received the same string that you sent. This check mitigates token replay attacks" }, { "name": "state", "value": "", "type": "query", "description": "A URL-encoded random string. The authorization flow will pass the same string back to the Callback URL using the ``state`` query string parameter. This process helps ensure that the callback you receive is a response to what you originally requested. It prevents malicious actors from forging requests.\n\nThe string can only contain alphanumeric characters, commas, periods, underscores, and hyphens. \n" }, { "name": "scope", "value": "", "type": "query", "description": "A URL-encoded space-delimited list of requested scopes. See the `Developer's Guide documentation on scopes `_ for a list of valid values you can provide.\n\nThe string you specify for this parameter must not exceed 2000 characters and it cannot contain more than 50 scopes. " }, { "name": "response_mode", "value": "", "type": "query", "description": "Specifies how the authorization response should be returned. Valid values are:\n\n- ``fragment`` - Encode the response parameters in the fragment of the redirect URI. A fragment in a URI is the optional part of the URI that appears after a ``#`` symbol, which refers to a specific section within a resource. For example, ``section`` in ``https://www.mysite.org/myresource#section``.\n- ``form_post`` - Embed the authorization response parameter in an HTML form.\n- ``query`` - Embed the authorization response as a query string parameter of the redirect URI. \n\nIf ``id_token`` is stated as ``response_type``, only ``form_post`` is allowed as ``response_mode``.'\n" }, { "name": "prompt", "value": "", "type": "query", "description": "Specifies how to prompt users for authentication. Possible values are: \n\n- ``login`` : Always prompt the user for authentication, regardless of the state of the login session. \n\n**Note:** If you do not specify this parameter, the system will not prompt the user for authentication as long as a login session is active. If a login session is not active, the system will prompt the user for authentication.\n" }, { "name": "authoptions", "value": "", "type": "query", "description": "A JSON object containing options that specify how to display the sign-in page. Refer the `Developer's Guide documentation on AuthOptions `_ for supported values." }, { "name": "code_challenge", "value": "", "type": "query", "description": "A URL-encoded string derived from the code verifier sent in the authorization request with the Proof Key for Code Exchange (PKCE) grant flow." }, { "name": "code_challenge_method", "value": "", "type": "query", "description": "The method used to derive the code challenge for the PKCE grant flow. Possible value is:\n\n- ``S256``- Hashes the code verifier using the SHA-256 algorithm and then applies Base64 URL encoding.\n" } ] }, "docs": "Returns a browser URL to redirect an end user in order to acquire the user’s consent to authorize the application to access resources on their behalf.\n\nInvoking this operation is the first step in authenticating users and retrieving an authorization code grant. The authorization code that is generated remains valid for 5 minutes, while the ID token stays valid for 60 minutes. Any access tokens you obtain are valid for 60 minutes, and refresh tokens remain valid for 15 days.\n\nThis operation has a" }, { "info": { "name": "Revoke Token", "type": "http" }, "http": { "method": "POST", "url": "https://developer.api.autodesk.com/authentication/v2/revoke", "headers": [ { "name": "Authorization", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Revokes an active access token or refresh token.\n\nAn application can only revoke its own tokens.\n\nThis operation has a rate limit of 100 calls per minute." }, { "info": { "name": "Get JWKS", "type": "http" }, "http": { "method": "GET", "url": "https://developer.api.autodesk.com/authentication/v2/keys" }, "docs": "Returns a set of public keys in the JSON Web Key Set (JWKS) format.\n\nPublic keys returned by this operation can be used to validate the asymmetric JWT signature of an access token without making network calls. It can be used to validate both two-legged access tokens and three-legged access tokens. \n\nSee the Developer's Guide topic on `Asymmetric Signing `_ for more information. \n" }, { "info": { "name": "Acquire Token", "type": "http" }, "http": { "method": "POST", "url": "https://developer.api.autodesk.com/authentication/v2/token", "headers": [ { "name": "Authorization", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Returns an access token or refresh token.\n\n* If `grant_type` is `authorization_code`, returns a 3-legged access token for authorization code grant. \n* If `grant_type` is `client_credentials`, returns a 2-legged access token for client credentials grant.\n* If `grant_type` is `refresh_token`, returns new access token using the refresh token provided in the request.\n\nTraditional Web Apps and Server-to-Server Apps should use the ``Authorization`` header with Basic Authentication for this operation. " }, { "info": { "name": "Introspect Token", "type": "http" }, "http": { "method": "POST", "url": "https://developer.api.autodesk.com/authentication/v2/introspect", "headers": [ { "name": "Authorization", "value": "" } ], "body": { "type": "form-urlencoded", "data": [ { "name": "token", "value": "" }, { "name": "client_id", "value": "" } ] } }, "docs": "Returns metadata about the specified access token or reference token.\n\nAn application can only introspect its own tokens.\n\nThis operation has a rate limit of 500 calls per minute." }, { "info": { "name": "Get OIDC Specification", "type": "http" }, "http": { "method": "GET", "url": "https://developer.api.autodesk.com/.well-known/openid-configuration" }, "docs": "Returns an OpenID Connect Discovery Specification compliant JSON document. It contains a list of the OpenID/OAuth endpoints, supported scopes, claims, public keys used to sign the tokens, and other details." }, { "info": { "name": "Logout", "type": "http" }, "http": { "method": "GET", "url": "https://developer.api.autodesk.com/authentication/v2/logout", "params": [ { "name": "post_logout_redirect_uri", "value": "", "type": "query", "description": "The URI to redirect your users to once logout is performed. If you do not specify this parameter your users are redirected to the Autodesk Sign-in page. \n\n**Note:** You must provide a redirect URI that is pre-registered with APS. This precaution is taken to prevent unauthorized applications from hijacking the logout process.\n" } ] }, "docs": "Signs out the currently authenticated user from the APS authorization server. Thereafter, this operation redirects the user to the ``post_logout_redirect_uri``, or to the Autodesk Sign-in page when no ``post_logout_redirect_uri`` is provided.\n\nThis operation has a rate limit of 500 calls per minute.\n" } ] } ], "bundled": true }