ACC Custom Integrations Setup

For RAPS to work with ACC account administration — adding and removing project members, updating roles, managing folder permissions, and running bulk operations across projects — your APS app must be registered as a Custom Integration in your ACC account.

This is a one-time setup step performed by an Account Administrator in the ACC web interface.

Why This Is Required

ACC account-level APIs (used by all raps admin commands) are protected by an additional authorization layer beyond standard OAuth. An APS app can only call these APIs after an Account Administrator explicitly grants it access through Custom Integrations.

Without this step:

raps admin user add / remove / update return HTTP 403
raps admin project list returns HTTP 403
Hub discovery during raps init may show no enterprise hubs

Prerequisites

You must be an Account Administrator in the ACC account, or ask one to perform these steps
You need the Client ID of your APS app (from aps.autodesk.com/myapps)

Setup Steps

1. Open Custom Integrations in ACC

Navigate to your ACC account and go to Account Admin → Custom Integrations:

https://acc.autodesk.com/account-admin/custom-integrations/

2. Add your app

Click “Add custom integration” (or “Add” if the account already has integrations).

3. Enter your Client ID

Paste your APS app’s Client ID into the field. You can find it in the APS Developer Portal under your app’s credentials.

4. Select access level

Choose “Full Account Access”.

This is required for RAPS to:

List and filter projects across the account
Add, remove, and update project members
Resolve role names to IDs
Manage folder permissions

5. Save

Click Save (or Confirm). The app is now authorized to make account-level API calls.

Finding Your Account ID

After registering, copy the Account ID shown on the Custom Integrations page — it’s the UUID listed next to your account name (e.g. 01fb1602-2ec0-4b05-bf6e-39dc70b3ae05).

Add it to your .env file so RAPS admin commands work without --account every time:

APS_ACCOUNT_ID=01fb1602-2ec0-4b05-bf6e-39dc70b3ae05

You can also retrieve it programmatically once you have admin access:

raps admin project list --limit 1 --output json | jq -r '.[0].relationships.hub.data.id'

Verifying the Setup

Run raps init or raps status after registering:

raps status

If the setup is correct, your ACC account will appear in the enterprise hub section and raps admin commands will work without 403 errors.

You can also do a quick test with:

raps admin project list --account YOUR_ACCOUNT_ID --limit 5

A successful response (project list or empty list) confirms the integration is active.

Access Levels

Level	What it allows
Full Account Access	All account and project APIs — required for RAPS admin commands
Custom	Granular scope selection — use only if your security policy requires it; you will need to manually enable the scopes RAPS depends on

Commands Enabled After Setup

Once registered, the following raps admin commands become available:

Command	Description
`raps admin user add`	Add user to multiple projects with role
`raps admin user remove`	Remove user from projects
`raps admin user update`	Update user role across projects
`raps admin user add-to-all-projects`	Onboard user to all active projects
`raps admin user list`	List account or project members
`raps admin folder set-permissions`	Set folder permissions in bulk
`raps admin project list`	List and filter projects
`raps admin project create`	Create a new project
`raps admin project archive`	Archive a project

Multiple Accounts

If you manage multiple ACC accounts, you must register your app separately in each account’s Custom Integrations. Each account’s Account Administrator must perform the setup independently.

Troubleshooting

403 AUTH-010 after registration

Your 3-legged OAuth token may be missing the account:write scope. Re-authenticate with the full scope preset:

raps auth login --preset all

App not appearing after save

It can take up to a minute for the integration to become active. Try again after a short wait.

“No enterprise hub found” in raps init

This usually means the integration has not been registered yet, or was registered under a different Client ID. Verify the Client ID in ACC Custom Integrations matches the one in your RAPS profile (raps config show).

raps init — First-time setup wizard that guides you through this step
raps admin — Full reference for all admin commands
raps auth login — Re-authenticate if you get scope-related 403 errors