Adobe User Management

Adobe User Management API provides comprehensive user lifecycle management capabilities for Adobe Creative Cloud and other Adobe services, enabling automated user provisioning, role management, and access control.

Power end-to-end data operations for your Adobe User Management API with Nexla. Our bi-directional Adobe User Management connector is purpose-built for Adobe User Management, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Adobe User Management or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Adobe User Management workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Adobe User Management credential in Nexla, you need to set up an OAuth Server-to-Server integration in the Adobe Developer Console and obtain the required credentials. This integration enables programmatic access to the Adobe User Management API without requiring user interaction.

OAuth Server-to-Server authentication provides secure, automated access to the Adobe User Management API without requiring user interaction. This authentication method is ideal for automated workflows and integrations. For additional information about setting up OAuth Server-to-Server integrations, see the Adobe Developer Console documentation.

1. Access Adobe Developer Console: Sign in to the Adobe Developer Console with an account that has administrative access to your Adobe organization.

2. Create a New Project: Create a new project or select an existing project in the Adobe Developer Console. Projects organize your API integrations and credentials.

3. Add API Integration: Add the User Management API to your project by selecting Add API and choosing User Management API from the list of available APIs.

4. Configure OAuth Server-to-Server: Enable OAuth Server-to-Server authentication for your integration. This authentication method is required for programmatic access to the User Management API.

5. Obtain Organization ID: Locate your Organization ID in the project details. The Organization ID is a unique identifier for your Adobe organization and follows the format A495E53@AdobeOrg. This ID is required for all User Management API requests.

   The Organization ID uniquely identifies your Adobe organization and is required for all User Management API operations. You can find this ID in your Adobe Admin Console or in the project details in the Adobe Developer Console. For detailed information about Adobe User Management API authentication, see the Adobe User Management API documentation.

6. Obtain Client Credentials: After configuring the OAuth Server-to-Server integration, you will receive a Client ID and Client Secret. These credentials are used to authenticate with the Adobe Identity Management System (IMS) and obtain access tokens for API requests.

Authenticate

Credentials required

Field	Required	Secret	Description
Organization Id	Yes	No	The unique identifier for an organization. This is a string of the form A495E53@AdobeOrg
Client ID	Yes	Yes	Enter your Adobe UM API Client ID. You can get it from the OAuth Server-to-Server enabled project on Adobe developer portal.
Client Secret	Yes	Yes	Enter your Adobe UM API Client Secret. You can get it from the OAuth Server-to-Server enabled project on Adobe developer portal.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Adobe User Management

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Adobe Organization ID in the Organization Id field. This should be the unique identifier for your Adobe organization, typically in the format A495E53@AdobeOrg. You can find this ID in your Adobe Admin Console or in the project details in the Adobe Developer Console.

4. Enter your OAuth Client ID in the Client ID field. This is the Client ID obtained from your OAuth Server-to-Server enabled project in the Adobe Developer Console. The Client ID is used to authenticate with the Adobe Identity Management System (IMS) and is included in the x-api-key header for all API requests.

5. Enter your OAuth Client Secret in the Client Secret field. This is the Client Secret obtained from your OAuth Server-to-Server enabled project in the Adobe Developer Console. The Client Secret is used together with the Client ID to obtain access tokens for API authentication.

   The Organization ID, Client ID, and Client Secret are required for all Adobe User Management API operations. These credentials should be kept secure and not shared publicly or committed to version control systems. The OAuth Server-to-Server flow automatically handles token exchange and refresh, providing seamless authentication for API requests.

   For detailed information about Adobe User Management API authentication and credential management, see the Adobe User Management API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Adobe User Management connector tile, then select the credential that will be used to connect to the Adobe User Management instance, and click Next; or, create a new Adobe User Management credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Adobe User Management endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Users in Organization

This endpoint retrieves a paginated list of all users in your Adobe organization along with detailed information about each user. Use this endpoint when you need to access user data for reporting, analysis, or integration with other systems.

• This endpoint automatically retrieves all users in your organization using pagination. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses page-based pagination, automatically fetching additional pages as needed. By default, the endpoint retrieves up to 2000 users per page, starting from page 0.
• The endpoint will return user information including email addresses, names, account status, and other user attributes for all users in your organization.

This endpoint supports pagination through page numbers. Nexla automatically handles pagination to retrieve all available users. For detailed information about the User Management API and available user attributes, see the Adobe User Management API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Adobe User Management data sources can also be manually configured to ingest data from any valid Adobe User Management API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, path to data, metadata, and request headers.

Adobe User Management API endpoints typically follow the pattern https://usermanagement.adobe.io/v2/usermanagement/{resource}/{organization_id}/{additional_path}, where {organization_id} is your Adobe Organization ID. For a complete list of available Adobe User Management API endpoints, see the Adobe User Management API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Adobe User Management data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Adobe User Management destination, and select the Send to Destination option from the menu. Select the Adobe User Management connector from the list of available destination connectors, then select the credential that will be used to connect to the Adobe User Management organization, and click Next; or, create a new Adobe User Management credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Adobe User Management endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create User (Adobe Id)

This endpoint creates new users in your Adobe organization who have existing Adobe IDs. Use this endpoint when you need to add users to your organization from your Nexset data. The endpoint automatically maps records with basic user information into the required payload structure.

• This endpoint automatically transforms your Nexset data into the required Adobe User Management API format. No additional configuration is required beyond selecting this endpoint template.
• Each record in your Nexset should include the following fields: email (required), country (optional), first (optional, for first name), and last (optional, for last name).
• The endpoint will create users with the provided information. If a user with the specified email already exists in the organization, the operation will be ignored (as configured by the ignoreIfAlreadyExists option).
• Each record in the Nexset will be sent as a separate API request to create a new user in your Adobe organization.

This endpoint is designed for users who already have Adobe IDs. The endpoint automatically handles the payload transformation, mapping your Nexset fields to the required API structure. For detailed information about creating users and available user attributes, see the Adobe User Management API documentation.

Remove Users from Org

This endpoint removes users from your Adobe organization. Use this endpoint when you need to remove user memberships from your organization based on your Nexset data. The endpoint can optionally delete the user account and associated assets if the account is owned by the organization.

• Each record in your Nexset should include an email field identifying the user to be removed from the organization.
• Select whether to permanently delete the account and assets in the Delete Account and Assets? field. If set to true, the user account and any associated assets will be permanently deleted if the account is owned by the organization. If set to false, only the user's membership in the organization will be removed.
• The endpoint will remove users from the organization based on the provided email addresses. Each record in the Nexset will be sent as a separate API request to remove the corresponding user.

Removing users from an organization is a permanent action. If you set "Delete Account and Assets?" to true, the user account and all associated assets will be permanently deleted and cannot be recovered. Use this option with caution. For detailed information about removing users, see the Adobe User Management API documentation.

Manual configuration

Adobe User Management destinations can also be manually configured to send data to any valid Adobe User Management API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Adobe User Management API endpoints typically expect JSON format for request bodies and follow the pattern https://usermanagement.adobe.io/v2/usermanagement/{resource}/{organization_id}, where {organization_id} is your Adobe Organization ID. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Adobe User Management endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Adobe User Management endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.