Create a Technical Account for Knowledge Base

A Technical Account provides application credentials for authenticating with Knowledge Base. Creating one combines Knowledge Base-specific access requirements with Adobe's standard developer and OAuth Server-to-Server credential workflows.

Before you begin

The person setting up the Technical Account must have:

• An Acrobat Studio for Enterprise license.
• Access to the applicable Acrobat Shared Credits product.
• Access to the Developer console.
• Access to Knowledge Base for the organization.

The technical account itself must be provisioned with:

• An Acrobat Studio for Enterprise license.
• Access to the applicable Acrobat Shared Credits product.

The person creating the API credential must also have developer access to the applicable product profile in Adobe Admin Console. Developer access grants permission to create API credentials and associate them with product profiles.

Learn how to add and manage developers in Adobe Admin Console.

Create the Technical Account credentials

Use Adobe's standard OAuth Server-to-Server credential workflow to create the credentials used by the Technical Account.

In Adobe Developer Console, create an OAuth Server-to-Server credential and associate it with the product profiles required by the integration.

Set up an OAuth Server-to-Server credential.

The OAuth Server-to-Server credential provides the client information your application uses to generate access tokens for authenticated API requests.

Manage API credential access

API credentials are associated with one or more product profiles. Those profile assignments determine the permissions available to API requests made with the credential.

Administrators can review and change these associations in Adobe Admin Console. Changing or removing a product-profile association can change or terminate the application's access to the associated product.

Manage API credentials for developers.

Use the Technical Account credentials

After the Technical Account is configured, applications can use its OAuth Server-to-Server credentials to authenticate supported Knowledge Base API requests.

Other developers working on the same integration do not need to create a separate Technical Account for the organization. Applications authenticate using the Technical Account credentials rather than an individual developer's interactive user session.

Continue setting up API access

Creating the Technical Account credentials is one part of configuring Knowledge Base API access.

After the credential is available, complete the Knowledge Base-specific authentication, permissions, and validation requirements for your application.

Set up Knowledge Base API access >

Technical Account considerations

• The initial Technical Account setup requires the applicable Studio license, shared-credit access, and Knowledge Base access.
• The person creating API credentials must have developer access to the applicable product profile.
• Product profiles associated with an API credential determine the permissions available to API calls.
• OAuth Server-to-Server credentials authenticate application requests independently of an individual developer's interactive session.
• Administrators can manage API credential product-profile assignments in Adobe Admin Console.
• Use the Knowledge Base API reference for current endpoints, request requirements, and schemas.