Who can use Developer Console and where their projects live: an enterprise organization, where an administrator grants developer access, or a personal developer organization created for any Adobe account.
Last checked 2026-09-30
CX Enterprise atlas / Developer & Extensibility | Developer & extensibility
Adobe Developer Console
ProductGenerally available
Developer & ExtensibilityDeveloper & extensibility
Also known as Adobe I/O Console, Adobe IO Console
Adobe's web portal (developer.adobe.com/console) where developers create projects for the applications they build against Adobe. A project holds the APIs, I/O Events registrations, I/O Runtime namespaces and plugins an application uses, together with the OAuth or API key credentials that call them. For enterprise organizations, access to an API is granted through Admin Console product profiles attached to the credential.
Built on 1
Integrates with 5
- Adobe Admin Console
- Adobe I/O Events
- Adobe Developer App Builder
- API Mesh for Adobe Developer App Builder
- Adobe Exchange
Integrated by 6
- Adobe Experience Manager Assets: Assets APIs
- Adobe Firefly Services: Platform and access
- API Mesh for Adobe Developer App Builder: API Mesh in Developer Console
- Adobe Developer App Builder: App Builder CDN, aio console commands, App Builder Logs in Developer Console
- Adobe I/O Events
- Adobe Admin Console: User Management API
Foundation for 1
Contains 7 parts, 60 entries
- Organizations and developer access# Collection
- Enterprise organization projects# Capability
Projects created in a company or school organization belong to the organization and are visible to its developers and system administrators. Users need the developer role (or system administrator role) before they can see or create projects; others can only view the Console and request API access.
Last checked 2026-09-30
- Personal developer organization# Capability
A private organization created automatically when someone signs in with a personal Adobe account. Projects in it are visible only to that user; templated projects, I/O Runtime and extra email alert recipients are not available there.
Last checked 2026-09-30
- Developer role for Console access# Capability
Also known as API Developer role
Admins assign users as developers on product profiles in Admin Console. The role lets them create and edit Console projects that use those profiles' APIs; anyone with access to a project's product profiles can view, edit and delete the project.
Integrates with: Developers and API credentials
Last checked 2026-09-30
- Admin developer role# Capability
An Admin Console role that works like the API developer role for Console projects and also allows adding the Admin Console Audit Logs event provider, whose event stream it protects.
Integrates with: Predefined roles
Last checked 2026-09-30
- API access requests# Capability
From the API catalog, a user without access can send a request to the organization's administrator for an API the organization has licensed; the request is approved or denied in Admin Console.
Integrates with: Product requests
Last checked 2026-09-30
- Organization switcher# Capability
Moves between the organizations in which the user is a developer or system administrator; the project list and the role shown follow the selected organization.
Last checked 2026-09-30
- Projects and workspaces# Collection
Also known as Developer Console projects
All work in Developer Console happens in a project, which stands for one application or integration and can combine APIs, events, Runtime and plugins from several Adobe products. Projects replaced the older "integrations" and plugin entries.
Last checked 2026-09-30
- Empty projects# Capability
A blank project to which the developer adds APIs, event registrations, Runtime or plugins directly, without workspaces. Available in personal and enterprise organizations.
Last checked 2026-09-30
- Templated projects# Capability
Projects created from a template, available to enterprise organizations only. Services are added per workspace rather than to the project as a whole.
Last checked 2026-09-30
- App Builder project template# Capability
The one template currently offered. It sets a public, unchangeable app name, creates Production and Stage workspaces and, by default, gives each workspace its own I/O Runtime namespace for building App Builder single-page apps and actions.
Integrates with: Developer App Builder
Last checked 2026-09-30
- Workspaces# Capability
Sub-environments of a templated project, each with its own services, credentials and Runtime namespace. Production is the workspace submitted for approval; Stage and extra per-developer workspaces are for development and testing.
Last checked 2026-09-30
- Project list, filters and export# Capability
Also known as Project Filters
Lists every project in the organization as cards or a table, sortable by creation, modification or last service activity. Filters cover text (project, client ID, technical account, event registration, plugin or Runtime namespace), creator, contents, projects needing attention and certificates expiring within 30 days; the list exports to CSV.
Last checked 2026-09-30
- Project activity log# Capability
Also known as Project Activity Logs
Records who changed what in a project and when, kept for one year and exportable to CSV. A separate organization-level log shows who deleted which project.
Last checked 2026-09-30
- Last service activity# Capability
The date Adobe last saw the project in use, based on access-token generation and event deliveries. It does not yet cover App Builder action invocations, API key use or Creative Cloud plugins.
Last checked 2026-09-30
- Read-only projects# Capability
Projects or workspaces a member can see but not change, download from or submit, because they use services or product profiles the member has no access to.
Last checked 2026-09-30
- Auto-generated projects# Capability
Projects that an Adobe product creates in the customer's organization for its own integrations. They are shown for transparency but no one, including system administrators, can edit or delete them.
Last checked 2026-09-30
- Project services# Collection
The things a project or workspace can contain: Adobe APIs, I/O Events registrations, an I/O Runtime namespace and Creative Cloud plugins. Access to many services depends on the organization's or user's licences.
Last checked 2026-09-30
- APIs and services catalog# Capability
Browsable tabs of every Adobe API, event provider (Adobe and custom), plugin type and Runtime offer, searchable and filterable by product. Services the organization is not licensed for are greyed out.
Last checked 2026-09-30
- Add an API# Capability
Adds an Adobe REST API to a project or workspace with the credential type the API supports (OAuth Server-to-Server, OAuth user authentication or API key) and, for enterprise APIs, the product profiles the credential may use. The API page links documentation and Postman files.
Last checked 2026-09-30
- I/O Management API# API / SDK
A Console service that lets a project's credential manage Adobe I/O resources programmatically: list, add and delete its own client secrets, and call the I/O Events provider, registration and journaling APIs.
Integrates with: I/O Events
Last checked 2026-09-30
- Event registrations in projects# Capability
Adds I/O Events to a project: pick an event provider and event types, attach an OAuth credential, and choose a webhook, Runtime action or journal as delivery. Each registration has registration details, credentials and debug tracing tabs.
Integrates with: I/O Events, Event registrations
Last checked 2026-09-30
- Runtime namespaces in projects# Capability
Enables Adobe I/O Runtime for an empty project or a workspace, which provisions a unique Runtime namespace. Runtime requires an enterprise licence and, once enabled, cannot be removed; a project with Runtime cannot be deleted.
Integrates with: I/O Runtime
Last checked 2026-09-30
- SDK downloads# Capability
Also known as Downloads
A Downloads tab listing SDKs for Adobe products with their documentation and configuration details, plus a history of the user's previous downloads.
Last checked 2026-09-30
- Creative Cloud plugin projects# Collection
Console projects for desktop app plugins, with a starter project, a plugin ID and a distribution flow to the plugin marketplace. Creative Cloud apps are outside this map, so these are listed only as integrations.
Last checked 2026-09-30
- Adobe XD plugins# Integration
Plugin projects for Adobe XD, packaged as .xdx files and submitted from the Console for review.
Last checked 2026-09-30
- Photoshop plugins# Integration
UXP plugin projects for Photoshop, packaged as .ccx files; paid listings require a FastSpring account in the public profile.
Last checked 2026-09-30
- Plugin versions and review# Capability
Plugin listings carry localised metadata, a plugin file under 50 MB and a version; Adobe reviews each submission within about 10 business days, and a new version replaces one still in review.
Last checked 2026-09-30
- Credentials# Collection
Also known as Developer Console credentials, Console credential types
The authentication credentials a project uses to call Adobe APIs and receive events, grouped by whose data they reach: the organization's (server to server), a signed-in user's (user authentication), a customer's through a partner app (admin authentication), or none (API key). The credential page shows client IDs, secrets, connected services and token generation.
Built on: Identity Management System
Last checked 2026-09-30
- OAuth Server-to-Server# Capability
Also known as OAuth S2S credential, Server-to-server credential
The credential for applications that act on their own or their organization's data (2-legged OAuth). It uses the OAuth 2.0 client_credentials grant with a client ID and secret, so tokens come from one call to Adobe IMS with standard OAuth libraries. Its technical account gets the product profiles chosen when the API is added.
Integrates with: OAuth Server-to-Server authentication
Last checked 2026-09-30
- Product profiles for API access# Capability
When an enterprise API is added, the developer picks the product profiles the credential's technical account joins; those profiles decide which features and data every API call can reach. Admins can change them later in Admin Console.
Integrates with: Product profiles, Developers and API credentials
Last checked 2026-09-30
- Credential name in Admin Console# Capability
Each OAuth Server-to-Server credential has a name that also appears in Admin Console under Users > API credentials, where admins manage every such credential in the organization.
Integrates with: Developers and API credentials
Last checked 2026-09-30
- Access token generation and scopes# Capability
The credential page generates a test access token and shows the cURL request for generating tokens in code, along with the scopes per service so a token can be limited to some of the project's services.
Last checked 2026-09-30
- Client secret rotation# Capability
A credential can hold more than one client secret. Developers add a new secret, switch the application over, check the old secret's last-used time and delete it, in the UI or programmatically through the I/O Management API.
Integrates with: I/O Management API
Last checked 2026-09-30
- Service Account (JWT) credential# Capability, deprecated
The former server-to-server credential, which signed a JWT with a certificate and private key pair that expired yearly. Deprecation was announced on 1 May 2023, new JWT credentials were blocked after 3 June 2024 and end of life was 30 June 2025. Remaining credentials are converted to OAuth Server-to-Server when their certificate expires or on 1 March 2026, whichever comes first.
Replaced by OAuth Server-to-Server
Integrates with: Service Account (JWT) credentials
Last checked 2026-09-30
- JWT to OAuth Server-to-Server migration# Capability
A zero-downtime migration card on the JWT credential page: add the OAuth credential alongside the JWT one, update the application, confirm the old credential is no longer used, then delete it. While a migration runs, services cannot be added and secrets cannot be rotated.
Last checked 2026-09-30
- Certificate expiry alerts# Capability, deprecated
Email alerts and a project filter for JWT public certificates expiring within 30 days, with steps to generate a replacement key pair and remove the old certificate. Relevant only while JWT credentials remain.
Replaced by Client secret rotation
Last checked 2026-09-30
- OAuth User authentication credentials# Capability
Also known as User authentication credentials
Credentials for applications that act on a signed-in Adobe user's data after the user consents (3-legged OAuth, authorization_code grant). Refresh tokens are issued with the offline_access scope. New credentials start In Development and may need Adobe approval before general use.
Integrates with: OAuth user authentication
Last checked 2026-09-30
- OAuth Web App credential# Capability
For applications with a backend server that keeps the client secret; supports refresh tokens. Requires a default redirect URI and a redirect URI pattern.
Last checked 2026-09-30
- OAuth Single Page App credential# Capability
For browser JavaScript apps without a backend, and mobile apps using a web view. No client secret; tokens come through the PKCE flow and there are no refresh tokens.
Last checked 2026-09-30
- OAuth Native App credential# Capability
For apps running natively on Android, iOS, Windows, macOS and other devices. No client secret; tokens come through the PKCE flow and there are no refresh tokens.
Last checked 2026-09-30
- OAuth Web, iOS and Android credentials# Capability, deprecated
The earlier platform-specific OAuth credentials. Web is replaced by Web App (which drops the implicit flow; Single Page App is the substitute), and iOS and Android are replaced by Native App.
Replaced by OAuth Web App credential
Last checked 2026-09-30
- Redirect URIs# Capability
A default redirect URI (up to 256 characters) and a redirect URI pattern (up to 512 characters) that any other requested redirect must match, both within the application's domain.
Last checked 2026-09-30
- Beta users# Capability
Up to 25 users, added by email or CSV, who can use an OAuth user authentication integration while it is In Development or In Review. Adobe does not contact them, and the list is cleared on approval.
Last checked 2026-09-30
- API key credential# Capability
A key with no secret that only identifies the application, for services that need no access token, such as API Mesh or Adobe Stock, and for embedded Adobe web experiences like the Adobe Express Embed SDK. It cannot generate tokens.
Last checked 2026-09-30
- Allowed origins# Capability
The website domains configured on an API key; Adobe servers reject browser requests whose Origin header is not on the list, so a copied key cannot be reused elsewhere.
Last checked 2026-09-30
- Enterprise Web App# Capability
Also known as Admin authentication credential
The admin authentication credential for Adobe Technology Partner Program partners. A customer admin installs the partner app and consents, which creates a technical account in the customer organization; the admin controls its reach through product profiles, and one partner credential serves many customers.
Integrates with: Admin authentication, Integration consent and access
Last checked 2026-09-30
- Credentials for Adobe MCP servers# Capability
Programmatic (headless) connections to the Adobe Analytics and Customer Journey Analytics MCP servers use a Console project with an OAuth Server-to-Server credential whose technical account is in a product profile with MCP Read-only Access or MCP Full Access (Full Access if the integration creates or updates components). Interactive AI clients sign in with Adobe IMS OAuth instead and need no Console project.
Integrates with: Analytics MCP server, Customer Journey Analytics MCP server
Last checked 2026-10-20
- Approval and distribution# Collection
How a finished project is released: internal approval of App Builder apps, Adobe review of integrations for public use, and plugin review. Projects with submitted APIs or apps cannot be deleted.
Last checked 2026-09-30
- App Builder app approval# Capability
The Production workspace of an App Builder project is submitted with app details; the organization's system administrators approve or reject it with a note, and approved apps are published for internal use.
Integrates with: App review and approval
Last checked 2026-09-30
- Approval for public applications# Capability
Integrations meant for general users are submitted for review by Adobe; once approved they are Published and can be offered through Adobe Exchange. OAuth credentials that do not need review can be pushed to production by the developer.
Integrates with: Developer Distribution
Last checked 2026-09-30
- Public profile# Capability
Also known as Developer account management
The organization's publisher details (name, website, description, logo) shown on app consent screens and plugin listings, required before any submission. A Commerce tab holds the FastSpring key for paid plugins.
Integrates with: Developer Distribution
Last checked 2026-09-30
- Monitoring and usage# Collection
Usage data, quotas and alerts that Developer Console keeps for each project.
Last checked 2026-09-30
- Insights# Capability
Per-project (or per-workspace) charts of API calls over time, calls by service and response codes, and, where Runtime is enabled, activations, error activations and duration by action.
Last checked 2026-09-30
- Quota usage# Capability
For APIs sold or trialled with a fixed allowance, the API page shows the share of quota used and the units consumed in the current period.
Last checked 2026-09-30
- Email alerts# Capability
Adobe emails system administrators, plus up to 20 added recipients in enterprise organizations, when it detects a potential or ongoing impact on a project, such as an unreachable event webhook or an expiring certificate. Alerts can be paused for non-critical projects.
Last checked 2026-09-30
- Developer tooling# Collection
SDKs, command-line tools and samples for working with Console projects and credentials outside the web UI.
Integrates with: I/O CLI
Last checked 2026-09-30
- Developer Console SDK# API / SDK
Also known as aio-lib-console
The open-source JavaScript library (@adobe/aio-lib-console) behind the aio console commands of the Adobe I/O CLI, which calls the Console API to manage organizations, projects, workspaces, credentials and services.
Integrates with: aio console commands
Last checked 2026-09-30
- Postman collections# Capability
API pages offer downloadable Postman environment files with the project's credentials, and the Tools guide explains generating OAuth tokens and running cURL samples in Postman.
Last checked 2026-09-30
- Authentication sample code# Capability
Node.js and Python samples for the OAuth flows and admin authentication, plus a list of recommended standard OAuth 2.0 libraries.
Last checked 2026-09-30