Skip to main content
This guide walks you through setting up API access for teams and standard organizations (non-enterprise). You’ll create a service user, get your credentials, and make your first API call in minutes.
If you’re part of an enterprise with multiple organizations, custom roles, or SSO, see the Enterprise quick start instead.

Step 1: Create a service user

  1. Go to Settings > Devin API in your organization and open the Service users tab
  2. Click Provision service user
  3. Choose a descriptive display name (e.g., “CI Pipeline”, “Monitoring Bot”)
  4. Select a role:
    • Admin — full access, including organization settings and membership
    • Member — can create and manage Devin sessions and most organization resources, but not organization settings or membership
Use the Member role for most automation. Only use Admin if your integration needs to manage org settings or other users.

Step 2: Copy your API key

  1. After you provision the service user, its API key is shown in a dialog
  2. Copy the key immediately — it starts with cog_ and won’t be shown again
  3. Store it securely as an environment variable:

Step 3: Make your first API call

Create a Devin session:
Find your organization ID at the top of the Settings → Devin API page.
Want sessions attributed to your user? By default, sessions are attributed to the service user. To create sessions on behalf of a specific user (so they appear in that user’s session list), add "create_as_user_id": "user_abc123" to the request body. This requires the Admin role (which includes the ImpersonateOrgSessions permission). See Session attribution for details.

Step 4: Common operations

List your sessions

Send a message to a running session

Manage knowledge

Permissions for teams users

Teams organizations have a simple permission model: For fine-grained role-based access control (RBAC), see the Enterprise quick start.

Next steps