This guide helps you understand and use developer hubs within Autodesk Platform Services (APS). Use developer hubs to manage your team's development activities, applications, and API access in one centralized workspace.
Demo
Getting started with developer hubs
Developer hubs are centralized workspaces in APS for managing your team's API access, applications, and usage. They provide better visibility and enable easier collaboration.
- Each developer hub connects to one team.
You cannot change this connection later. - APS subscription is required to create or join a hub.
Choose your path:
1. Create your first developer hub (Check eligibility - Detailed information here )
Only team admins can create developer hubs. Each team can have one developer hub.
- Go to Autodesk Account > Products and Services > Hubs.
- Click Create hub.
- Select Autodesk Platform Services as the product.
- Enter your hub name and description.
- Click Create & Activate.
As the hub creator, you automatically become the first hub admin.
2. Join an existing team hub
Ask your team admin to invite you to your team's existing developer hub.
- Your hub admin sends you an invitation email.
- Accept the invitation to join the hub.
- Click Developer hub in the top right of the Autodesk Platform Services site to access your hub.
Keep in mind
- Any team admin can create a hub.
- A hub is always created within a team context.
- Each team can only have one hub.
- You cannot change which team your hub connects to after creation.
Managing hub members
Hub admins can invite team members, assign roles, and manage access to the developer hub.
Add team members to a hub
- In your developer hub, go to Roles and access > Hub members.
- Click Add member.
- Enter the user's email address.
- Select their role from the dropdown menu:
- Hub admin: Full management privileges
- Developer: Can edit owned apps and collaborate on shared apps
- Click Send invitation.
The user receives an email and must accept to join the hub.
Change hub member roles
- Go to Roles and access > Hub members.
- Find the member in the list.
- Click the Access level dropdown next to their name and select the new role.
The change takes effect immediately.
To work with external collaborators
External collaborators can access specific applications without being hub members.
- Go to Roles and access > External collaborators.
- Click Add collaborator.
- Enter their email address.
- Select which applications they can access.
- Choose their role for each application:
- App owner: Full control including editing, deleting, transferring
- App editor: Can edit the app and view usage reports
- App viewer: Read-only access to view app and usage reports
- Click Send invitation.
To remove members from a hub
- Go to Roles and access > Hub members.
- Find the member you want to remove.
- Click Remove next to their name.
- Confirm the removal.
Things to keep in mind
- Hub admins can remove any member, including other admins.
- A hub must always have at least one admin.
- Members who own apps cannot be removed until app ownership is transferred.
Managing applications
Hub admins and app owners can create, configure, and manage applications within the developer hub.
To create and configure an app
- In your developer hub, go to Applications.
- Click Create application.
- Enter your app name and description.
- Select your application type.
- Configure your callback URLs and other settings.
- Select which APIs your app can access.
- Click Create.
Your app will appear in the Applications section with two tabs:
- App settings: Manage credentials, permissions, and collaborators
- API usage: View usage metrics for this app
To transfer app ownership
Only hub admins and app owners can transfer ownership.
- Go to Applications and select your app.
- Click the menu and select Transfer ownership.
- Enter the new owner's email address.
- Click Transfer.
The new owner receives an email and must accept the transfer.
If the new owner is not a hub member, they'll choose where to host the app.
To move apps between hubs
You can move apps between hubs or to your My Applications page.
- Go to Applications and select your app.
- Click the menu and select Move app.
- Choose the destination:
- Another hub you have access to
- Your My Applications page
- Confirm the move.
Requirements to move an app
- You must be the app owner or a hub admin.
- You must be a member of both the source and destination hubs.
To manage app collaborators
App owners can add collaborators to specific applications.
- Go to Applications and select your app.
- Go to the App settings tab.
- Scroll to Collaborators.
- Click Add collaborator.
- Enter their email and select their role.
- Click Add.
Important: Moving an app does not change its ownership. The app owner remains the same regardless of which hub hosts the app.
Understanding analytics and reporting
Monitor your team's API usage and track application performance through hub analytics and app-level reporting.
To view hub analytics
Hub analytics show your team's overall API consumption.
- In your developer hub, go to Hub analytics.
- Use the tabs to switch between:
- Token usage: Track token consumption across all hub applications
- API usage: Monitor specific API calls and interactions
- Use filters:
- Applications: View usage for specific or all apps
- APIs: Focus on specific services
- Date range: Select the period to report
- Click Download to export usage data.
To monitor app-level API usage
- Go to Applications and select your app.
- Click the API usage tab.
- Review usage metrics and charts.
- Filter by API type and date range.
- Download detailed usage reports as needed.
How usage data works when moving apps
App-level reporting:
- Historical usage stays with the app, no matter its location.
- App usage reports remain the same after moving.
- All historical data is accessible to the app owner.
Hub-level reporting:
- Usage appears in the original hub's reporting for the period it occurred.
- No retroactive changes—historical usage does not transfer, only future usage after the move shows up in the new hub.
Key principle:
Usage is time-stamped and location-stamped. Data always reflects where and when API calls were made.
Troubleshooting
Can’t see your team’s developer hub?
- You may not be a member yet—ask your hub admin to invite you.
- Your team may not have a hub created—ask your team admin to create one.
- Check if you’re in the correct team if you belong to more than one.
Can’t create a developer hub?
- Only team admins can create developer hubs.
- Ask your team's primary or secondary admin to create the hub or request admin access if required for your role.
I moved my app but don't see its historical usage in the new hub. Is this a bug?
- This is expected. Historical usage remains in the original hub; new usage appears in the new hub.
Why can't I remove a hub member?
- Members who own apps can’t be removed until they transfer app ownership to another member.
Where are my shared apps?
- Go to your user profile menu and select Shared apps. These are apps shared with you from hubs where you're not a member.
Can external collaborators see all hub apps?
- No, they only see specific apps you share with them and cannot view other hub applications or member info.
Reference
Glossary
- Autodesk Platform Services (APS): The APIs and tools for developing applications that integrate with Autodesk products.
- App collaborator: A user with viewer or editor permissions on a specific application within a hub.
- App editor: Can edit and view usage reports for an app; cannot delete or transfer ownership.
- App owner: Full control of an app—including editing, deleting, transferring ownership, and moving between locations.
- App viewer: Read-only access to an app and its usage reports.
- Developer hub: Centralized APS workspace connecting a development team.
- External collaborators: Non-team users with access to specified apps only.
- Hub admin: Can manage all applications, members, and permissions in a hub.
- Hub member: Team user with access to the developer hub.
- My applications: APS page showing apps you own that aren't in a hub, plus apps shared with you.
- Shared apps: Apps shared with you from hubs where you're not a member, accessible via profile menu.
- Team: Container in Autodesk Account for managing products, services, and users. Each team may have one developer hub.
- Team primary admin: The designated admin with full control over a team (one per team).
- Team secondary admin: Additional admins with team user/product visibility (multiple per team).
Hub roles and permissions
Hub admin
- Invite/remove hub members
- Change roles
- Access hub usage reports
- View lists of admins and developers
- Edit all hub apps
- Transfer app ownership
- Move apps between locations
- Access app-level usage reports
Developer
- Edit owned apps in the hub
- View or edit collaborative apps
- Access app-level usage reports
Team admin
- Create a developer hub
- View hub profile in Autodesk Account
- Automatically become hub admin when creating the hub
App-level roles and permissions
App owner
- Edit, delete the app
- Transfer app ownership
- Move app between locations
- View app-level usage reports
- Manage collaborators
App editor
- Edit the app
- View app-level usage reports
App viewer
- View the app
- View usage reports