Skip to main content
This page tracks changes specific to Devin’s APIs (v1, v2, and v3). For application feature releases, see Application Release Notes.

​
2026

​
January 2026
v3 API Updates
  • Active users endpoint (Jan 9): Added GET /v3beta1/enterprise/metrics/active-users endpoint for retrieving unique active users for a custom date range. Unlike the DAU/WAU/MAU endpoints which return lists broken down by period, this endpoint returns a single count of unique active users across the entire specified range. Supports filtering by organization IDs and configurable activity thresholds (min_sessions, min_searches).

​
2025

​
December 2025
v3 API Updates
  • Session archive endpoint (Dec 11): Added POST /v3beta1/organizations/{org_id}/sessions/{devin_id}/archive endpoint for archiving sessions. Also added archive query parameter to DELETE /v3beta1/organizations/{org_id}/sessions/{devin_id} (terminate session) and is_archived field to session responses.
  • Order parameter removal (Dec 11): Breaking change: Removed the order query parameter from the sessions list endpoint (GET /v3beta1/organizations/{org_id}/sessions). Clients must stop sending order; use cursor-based pagination with first/after parameters instead.
  • Advanced sessions support (Dec 8): Added support for advanced session modes (analyze, create, improve, batch, manage) with new request parameters: advanced_mode, child_playbook_id, session_links, and bypass_approval. Session responses now include child_session_ids, parent_session_id, and is_advanced fields.
  • Searches router (Dec 10): Added enterprise and organization-level search endpoints at GET /v3beta1/enterprise/searches and GET /v3beta1/organizations/{org_id}/searches for listing searches with pagination and filtering.
  • Audit logs improvements (Dec 10): Added data object, service_user_name, and user_email fields to audit log responses. Added update_git_permission action type.
  • Session Tags router (Dec 5): Added CRUD endpoints at /v3/beta/enterprise/organizations/{org_id}/tags for managing allowed session tags per organization. When tag validation is enabled, session creation and tag updates enforce tags from the allowed list.
  • Enterprise Sessions endpoint (Dec 5): Added GET /v3/beta/enterprise/sessions to list sessions across the enterprise with optional org_ids filtering.
  • Git Permissions updates (Dec 5): Added prefix_path field for matching repositories by path prefix. Added PUT and DELETE endpoints for bulk replacing or clearing all permissions for an organization.
  • Session impersonation (Dec 5): Added create_as_user_id parameter to the session creation endpoint, allowing service users to create sessions on behalf of other users.
  • Hypervisors response change (Dec 5): The hypervisors endpoint response now returns utilization_percentage instead of max_slots and available_slots.
  • Notes and Playbooks routers (Dec 1): Added enterprise and organization-level Notes and Playbooks management endpoints to v3 API. Notes endpoints require ManageAccountKnowledge permission, Playbooks endpoints require ManageAccountPlaybooks permission.
v2 API Updates
  • Sessions messages field (Dec 11): Added messages field to v2 sessions API response, providing all session messages similar to the v1 API.
  • Response schema improvements (Dec 11): Added proper response schemas for audit logs, snapshots, and playbook endpoints including AuditLogsResponse, EnterpriseSnapshotResponse, and EnterprisePlaybookResponse.
v1 API Updates
  • Audit logs deprecation (Dec 5): The /v1/audit-logs endpoint is deprecated; use the v2 or v3 audit logs endpoints instead.
​
November 2025
v2 Enterprise API Updates
  • Pagination limit update (Nov 21): Maximum pagination limit reduced from 1000 to 200 items per request for improved performance and reliability. Default limit remains 100. This change does NOT affect the v1 External API.
  • Sessions router (Nov 16): Added comprehensive sessions management endpoints to v2 API for enterprise administrators.
  • Snapshots API endpoint (Nov 3): Added endpoint for retrieving snapshot details programmatically.
v1 API Updates
  • Terminate session endpoint (Oct 31): Added endpoint to terminate running sessions programmatically.
​
October 2025
v3 API Launch (Beta)
  • API v3 launch (Oct 23): Launched v3 API with full RBAC support, service user authentication model, and comprehensive audit logging for service user actions.
v2 Enterprise API Updates
  • Snapshot creation endpoint (Oct 30): New V2 Enterprise Organizations API endpoint for enterprise admins to programmatically clone repositories and create snapshots with custom setup steps and startup commands.
  • Playbooks API improvements (Oct 14): Added API for publishing enterprise playbooks with improved functionality for programmatic playbook management.
​
September 2025
v2 Enterprise API Updates
  • Roles router (Sep 25): Added enterprise roles router with five API endpoints for managing roles programmatically.
v1 API Updates
  • Playbooks API (Sep 6): Added comprehensive Playbooks API endpoints to v1 for creating, updating, listing, and deleting playbooks programmatically.
  • Secrets endpoint (Sep 5): Added new POST /v1/secrets endpoint for creating secrets via API.
​
March 2025
v2 Enterprise API Launch
  • API v2 launch (Mar 23): Launched Enterprise API v2 for enterprise administrators with organization management, consumption tracking, and member management capabilities.

​
2024

​
October 2024
v1 API Launch (Oct 26)
  • Launched REST API for programmatic session creation and management
  • Session creation, monitoring, and management endpoints
  • File attachment upload and download support
  • Basic authentication with API keys
  • Idempotent session creation support
  • Use cases: automatic PR reviews, lint error resolution, migrations

​
API Versioning Policy

​
Backward Compatibility

We strive to maintain backward compatibility within major versions. Breaking changes will be:
  1. Announced at least 7 days in advance
  2. Documented in these release notes
  3. Accompanied by migration guides when applicable

​
Deprecation Process

When we deprecate an API feature:
  1. Announcement: We’ll announce the deprecation with a timeline
  2. Deprecation Period: The feature remains available but marked as deprecated
  3. Removal: The feature is removed after the deprecation period

​
Version Support

  • v1: Generally available, actively maintained
  • v2: Generally available, actively maintained
  • v3: Beta - subject to changes, not recommended for production use yet

​
Migration Guides

​
Migrating from v1 to v3

If you’re building new integrations that require fine-grained permissions, consider using v3 instead of v1: Key Differences:
  • Authentication: v3 requires service user tokens instead of personal/service API keys
  • Authorization: v3 provides full RBAC with role-based permissions
  • Endpoints: v3 uses different URL patterns (/v3beta1/* instead of /v1/*)
Migration Steps:
  1. Create a service user in Enterprise Settings > Service Users
  2. Assign appropriate roles to the service user
  3. Generate an API key for the service user
  4. Update your integration to use v3 endpoints
  5. Test thoroughly in a non-production environment
View v3 API Documentation →

​
Migrating from v2 to v3

v3 provides more flexibility than v2 for enterprise automation: Key Differences:
  • Authentication: v3 uses service users instead of requiring Enterprise Admin personal keys
  • Authorization: v3 supports granular RBAC instead of enterprise-admin-only access
  • Scope: v3 can be scoped to specific organizations, v2 is always enterprise-wide
When to Migrate:
  • You need automation with non-admin permissions
  • You want to scope API access to specific organizations
  • You need clear separation between human and service accounts
  • You require detailed audit trails for automated actions

​
Support

For questions about API changes or migration assistance: