Before you begin
Make sure you have:- A Box developer account with access to the
- A sense of how your application runs: as a server backend or a user-facing app (see )
On a free developer account, a default CCG application is created and authorized automatically. See on the free developer plan page. The steps below apply when you create additional applications or when an enterprise admin must authorize your app.
Create your first application
- Go to the .
- Select New App.
- Enter your application name.
- Choose the application type: Server or User.
- Server: Select the authentication method: Client Credentials Grant (CCG) or JSON Web Token (JWT).
- User: The authentication method is automatically set to OAuth 2.0.
- Select Create.
Configure the application
On the Configuration tab, set the options your application needs:- App Access Level — Controls whether the app can act only as its service account or also on behalf of enterprise users. See for Client Credentials Grant apps.
- Application Scopes — Enable only the permissions your app requires. Add scopes before you authorize the app in the Admin Console.
- Additional Configuration — Toggle advanced features such as Generate User Access Tokens when your server app must act as a specific user.
- CORS Domains — Add domains if your application accesses Box resources from a browser on another origin.
App details and credentials
Still on the Configuration tab, open App Details to view and copy credentials:- Application status
- Service accounts (for authorized server applications)
- Client ID, Client Secret, and Developer Token
- Collaborators (if you added any)
- Properties, including your user ID and enterprise ID
Your user ID and enterprise ID appear in the Properties section. To find IDs for other users, files, or folders, see .
Free developer accounts: You can add application collaborators who already have a Box account (for example, a teammate’s developer account, personal account, or enterprise account). To collaborate with a larger team in an isolated environment, ask your Box admin about a or .This is separate from content collaborators on files and folders. You can still invite existing Box users to content through the web app or .
Other Developer Console tabs
After configuration, use the other tabs as needed:- Webhooks — Register event triggers for your application
- App Diagnostics — Review recent API activity for the application
Optional: Publish to Integrations
When your app is ready for customers, see for the Developer Console submission flow and for the full checklist, assets, and partner review.What’s next
- and wire it into your codebase
- to test before production deployment
- for user, enterprise, file, and folder IDs used in API calls
- when you need more storage, higher limits, or additional features