Request

Response

    Known Issues

    Last updated: 25 May 2026

    This page lists limitations, behavioral gotchas, and entitlement requirements for Secure Service Accounts (SSAs) with Autodesk Platform Services (APS) APIs. Most entries come from customer reports. Review them before integrating.

    If you encounter behavior that is not listed here, see Reporting a new issue at the bottom of this page.


    How to read this page

    Each issue entry uses the same fields:

    • Status — whether the API is supported, partially supported, has a workaround, or requires specific configuration.
    • Who is affected — who encounters the issue, and when.
    • What you see — what happens when you hit the issue.
    • What you can do — how to fix it or work around it.
    • Tracking (when applicable) — the internal ticket or roadmap note.
    • Last verified — the date the behavior was last confirmed.

    Start with the Summary table to find your API, then open the matching section for symptoms and workarounds.


    Summary

    Issue areaStatusSummary
    Admin API Partially supported Includes Account Admin (BIM 360) and Hub Admin (Forma). Most operations support two-legged and three-legged access tokens. /hq/v1/ operations accept only two-legged OAuth by default; six /hq/v1/ operations can be enabled for three-legged access token support, which also enables SSA access, per Client ID.
    Automation API Partially supported Creating, monitoring, and canceling WorkItems require a two-legged access token because three-legged access tokens are not supported. For RCW models in jobs, data:read and data:write are enough to open files; code:all is needed only to run the job. Revit Design Automation WorkItems that open RCW models need BIM Collaborate Pro on the SSA.
    Forma Site Design API (Beta) Not supported SSA support is not on the current roadmap for Forma Site Design API (Beta).
    Sheets, Forms, Issues, and Photos APIs Workaround available Require a Forma Build subscription on the SSA at the account level. Success on Assets does not imply success on these modules.
    Review API Workaround available Requires Forma Data Management permissions on the SSA. These permissions must be assigned manually because they are not applied automatically.
    Forma Files API (Custom Attributes) Conditional Edit operations may require a Forma Files license on the SSA.
    Revit Cloud Worksharing License requirement Reads need BIM Collaborate; reads and writes need BIM Collaborate Pro, plus view and download permission on the model folder. If you cannot license the SSA, publish the model out of RCW state as a fallback.
    APS app configuration Configuration requirement Only Server-to-Server APS apps support SSA. Traditional Web App does not.
    SSA account limit Configuration requirement The default limit is 10 SSAs per Client ID. Request a higher limit through Get Help on the APS portal (ADN membership required).
    Token type confusion Common mistake The two-legged access token from step 1 of the handshake is sent instead of the final three-legged access token.

    Admin API

    The Admin API includes operations under Account Admin in the BIM 360 API reference and under Hub Admin in the Forma API reference.

    What to expect: Most Admin API operations support both two-legged and three-legged access tokens, including those obtained via SSA. The main exceptions are operations whose paths include /hq/v1/. By default, these operations accept only two-legged OAuth.

    Six /hq/v1/ operations are eligible for three-legged access token support on a per-Client-ID basis (see the next section). All other /hq/v1/ operations remain two-legged OAuth only.

    Note: SSA does not use a separate authentication mode from three-legged OAuth. An SSA obtains a three-legged access token through the SSA handshake (see API Basics). When Autodesk enables three-legged access token support on an operation, SSA access to that operation is enabled as well.

    /hq/v1/ operations (two-legged OAuth only)

    Some Admin API operations use the legacy BIM 360 HQ path pattern, /hq/v1/. By default, all of these operations accept only two-legged OAuth.

    The six operations eligible for three-legged access token support can be used with SSA once enablement is granted. Once enabled, those six operations no longer accept two-legged OAuth. All other /hq/v1/ operations continue to require two-legged OAuth.

    • Status: Limitation
    • Who is affected: You, if your app calls any Admin API operation whose path includes /hq/v1/.
    • What you see: Your three-legged access token does not work on /hq/v1/ operations, including the six operations listed below that can be enabled for it.
    • What you can do: For the standard /hq/v1/ operations, use a two-legged OAuth token. To use an SSA on the six eligible operations, ask us to enable three-legged access token support for them, as described below.
    • Last verified: May 2026

    Requesting three-legged access token support (enables SSA)

    The six /hq/v1/ operations eligible for three-legged access token support (listed below) are the only Admin API paths that can currently receive this enablement on a per-Client-ID basis.

    Six /hq/v1/ operations eligible for three-legged access token support

    • GET  /hq/v1/accounts/{account_id}/companies/search
    • GET  /hq/v1/accounts/{account_id}/users
    • GET  /hq/v1/accounts/{account_id}/projects/{project_id}/companies
    • POST /hq/v1/accounts/{account_id}/companies
    • POST /hq/v1/accounts/{account_id}/companies/import
    • POST /hq/v1/accounts/{account_id}/users

    How to request enablement

    Submit a single request through Get Help on the APS portal. See Reporting a new issue for ADN membership requirements. Include your Client ID and ask us to enable three-legged OAuth on the six /hq/v1/ operations listed above. Once granted, those six operations no longer accept two-legged OAuth. All other /hq/v1/ operations still require two-legged OAuth.

    Enabling three-legged OAuth on these operations also enables SSA, because the SSA flow produces three-legged access tokens for use on those operations.


    Automation API

    The Automation API was formerly known as the Design Automation API.

    What to expect: SSA works with most Automation workflows. WorkItem management and Revit Cloud Worksharing (RCW) have extra requirements — see below and Revit Cloud Worksharing.

    WorkItem management not supported with three-legged access tokens

    Creating, monitoring, and canceling WorkItems require a two-legged access token. Three-legged access tokens are rejected.

    • Status: Not supported
    • Who is affected: You, if you create, monitor, or cancel WorkItems.
    • What you see: WorkItem calls fail when you send a three-legged access token.
    • What you can do: Use a two-legged access token to manage WorkItems. You can still use a three-legged access token for any Forma or BIM 360 data the WorkItem works with.
    • Last verified: May 2026

    Token scope confusion when accessing RCW models

    For RCW models inside an Automation job, data:read and data:write are enough to open the file. code:all is only required to run the job.

    • Status: Documentation gap
    • Who is affected: You, if you run Automation Service (Design Automation) jobs that open RCW models.
    • What you see: It’s easy to assume you need the code:all scope just to open RCW files in a job. You don’t.
    • What you can do: To open RCW files, data:read and data:write on a three-legged access token are enough. You only need code:all to run the job.
    • Last verified: February 2026

    Revit Design Automation against RCW requires BIM Collaborate Pro

    Revit Design Automation WorkItems that open RCW models require BIM Collaborate Pro on the SSA.

    • Status: License requirement
    • Who is affected: You, if your Revit Design Automation WorkItems open RCW models.
    • What you see: Your WorkItems fail even though your access tokens look fine. The real problem is that your SSA does not have the required Revit license.
    • What you can do: Give the SSA a BIM Collaborate Pro license.
    • Last verified: July 2025

    Forma Site Design API (Beta)

    SSA support for Forma Site Design API (Beta) is not on the current roadmap.

    • Status: Not supported
    • Who is affected: You, if you want to use an SSA with any Forma Site Design API (Beta) operation.
    • What you see: You cannot link an SSA to this API.
    • What you can do: There is no workaround right now.
    • Last verified: July 2025

    Sheets, Forms, Issues, and Photos APIs

    What to expect: Each Forma Build module enforces entitlements separately. One module may accept your SSA access token while another returns 403.

    Sheets, Forms, Issues, and Photos require a Forma Build subscription on the SSA. Success on Assets does not imply success on these modules.

    • Status: Workaround available
    • Who is affected: You, if you use the Forma Build Sheets, Forms, Issues, or Photos API.
    • What you see: You get a 403 ERR_AUTHORIZATION_ERROR on any of these APIs, even though the same access token works for other Build APIs (such as Assets or RFI) in the same project.
    • What you can do: Give the SSA a Forma Build subscription at the account level before you call these APIs.
    • Last verified: March 2026

    Review API

    The Review API requires Forma Data Management permissions on the SSA. Other Forma APIs do not require these permissions.

    • Status: Workaround available
    • Who is affected: You, if you use the Forma Review API.
    • What you see: The Review API rejects your SSA access token, even though other Forma APIs accept it.
    • What you can do: Assign Forma Data Management permissions to the SSA manually — they are not applied automatically.
    • Last verified: June 2025

    Forma Files API (Custom Attributes)

    Editing custom attributes through the Forma Files API may require a license on the SSA. License enforcement can resume without notice.

    • Status: Conditional
    • Who is affected: You, if you edit custom attributes (for example, with POST .../custom-attributes:batch-update).
    • What you see: Your edit calls fail because the SSA does not have a Forma Files license.
    • What you can do: Give the SSA a Forma Files license before you edit data.
    • Tracking: A backend feature flag may disable this check temporarily, so it might work today and fail later — assign the SSA a license from day one to stay safe.
    • Last verified: February 2026

    Revit Cloud Worksharing

    What to expect: RCW operations through an SSA need the correct access token scopes and the correct BIM Collaborate license. See Automation API for RCW-related Automation issues.

    License required

    • Status: License requirement
    • Who is affected: You, if you perform RCW work through an SSA, including through the RCM API.
    • What you see: Your RCW reads or writes fail because the SSA does not have the required license.
    • What you can do: Give the SSA BIM Collaborate to read, or BIM Collaborate Pro to read and write. Also give the SSA view and download permission on the model folder.
    • Last verified: May 2026

    Fallback: publish RCW models out of RCW state

    • Status: Workaround
    • Who is affected: You, if you cannot give your SSA an RCW license.
    • What you see: Your SSA cannot access the model without that license.
    • What you can do: Publish the model out of its RCW state. Once you do, it becomes a regular Forma file that your SSA can reach.
    • Last verified: May 2026

    APS app configuration

    Only the Server-to-Server APS app type supports SSA provisioning.

    • Status: Configuration requirement
    • Who is affected: You, if you’re setting up a Forma Custom Integration.
    • What you see: You created a Traditional Web App expecting it to support SSA, but provisioning fails or is not available.
    • What you can do: Create a Server-to-Server APS app instead.
    • Last verified: May 2026

    SSA account limit

    Each Client ID supports up to 10 SSAs by default.

    Default cap of 10 SSAs per Client ID

    • Status: Configuration requirement
    • Who is affected: You, if you need more than 10 SSAs under one Client ID.
    • What you see: When you try to create an eleventh SSA, you get a quota error.
    • What you can do: Ask us to raise the limit through Get Help on the APS portal (see Reporting a new issue for ADN membership requirements). Tell us your Client ID, the limit you need, and a brief note on why.
    • Last verified: October 2025

    Token type confusion

    The SSA handshake produces two access tokens. Only the three-legged access token works for most business APIs.

    Sending the wrong access token from the SSA handshake

    • Status: Common mistake
    • Who is affected: You, if you send the wrong access token to an SSA-protected operation.
    • What you see: You see errors such as “SSA does not work with the Issues API.” Usually, this means you sent the two-legged access token from step 1 of the handshake instead of the final three-legged token. Some APIs accept the two-legged token anyway, so everything looks fine until you call a stricter API.
    • What you can do: Before you call business APIs, exchange the two-legged access token and JWT assertion for a three-legged access token. See JWT Assertions for how the flow works.

    Reporting a new issue

    If you encounter behavior not listed here, report it through Get Help on the APS portal.

    Note: You must have an active Autodesk Developer Network (ADN) membership before you can raise a support ticket through Get Help on the APS portal.

    Include the following in your report:

    • The API and operation (method and path).
    • The SSA Client ID and, if relevant, serviceAccountId.
    • Request and response headers, HTTP status code, and error body.
    • A timestamp with time zone for the failing request.