If you’re on a teams plan with a single organization and don’t need custom roles, the Teams quick start is simpler.
If you are a Devin Enterprise customer with a dedicated deployment, you will need to replace
api.devin.ai in all API URLs with your organization’s custom API domain (e.g., api.your-company.devinenterprise.com). Contact your Devin administrator or Cognition support if you are unsure of your API domain.Understanding service user scopes
Enterprise customers can create service users at two levels:
An enterprise service user with enterprise-level permissions automatically inherits the corresponding org-level permissions across all organizations.
Step 1: Create a service user
Enterprise service user (cross-org access)
- Go to Enterprise settings > Devin API and open the Service users tab
- Click Provision > Enterprise service user
- Choose a display name (e.g., “Analytics Dashboard”, “Org Provisioning Bot”)
- Assign an enterprise role with the permissions your integration needs, and choose an expiration
Organization service user (single-org access)
- Go to Settings > Devin API within the target organization and open the Service users tab
- Click Provision service user
- Choose a display name, assign an org-level role, and choose an expiration
Step 2: Copy your API key
- After you provision the service user, its API key is shown in a dialog
- Copy the key immediately — it starts with
cog_and won’t be shown again - Store it securely as an environment variable:
Step 3: Make your first API call
Enterprise endpoint example
List all organizations in your enterprise:Organization endpoint example
Create a Devin session in a specific org:Permissions and RBAC
Every API endpoint exceptGET /v3/self is gated by a specific permission. The required permission is documented on each endpoint’s API reference page. Permissions are split into two scopes:
- Enterprise permissions — control
/v3/enterprise/*endpoints (e.g.,ManageOrganizations,ManageBilling,ViewAccountMetrics) - Organization permissions — control
/v3/organizations/{org_id}/*endpoints (e.g.,UseDevinSessions,ManageOrgSecrets,ManageOrgPlaybooks)
ViewAccountSessions grants ViewOrgSessions in every org.
For the full permissions reference, see the permissions and RBAC documentation.
Common enterprise workflows
Monitor consumption across orgs
Audit log retrieval
Manage users across organizations
Next steps
- Browse the full API permissions reference
- Learn about authentication in depth
- Set up pagination for large result sets
- Review the migration guide if you’re moving from v1/v2

