A small collection of Adobe services (e.g. Adobe Stock) require authorization, but do not require authentication. These services can be called “anonymously” and typically provide consistent results regardless of the application or user that made the request. An API Key is the only client credential required for these services. These integrations do not need to pass an access token with each request.
To obtain an API Key, you'll need to create an API Key Integration using the Adobe I/O Console, as described here. If your integration needs to access Adobe services or content on behalf of a user or an Adobe enterprise organization, it needs additional credentials for authentication. For more information, check out the articles on OAuth Authentication and Service Account Authentication.
This article will walk you through the steps to set up an API Key integration.
Step 1: Subscribe to an Adobe Service
Step 2: Configure an API Key Integration
- To create a new API Key integration, sign in to the Adobe I/O Console with your Adobe ID, and click New Integration. (Notice that you may also choose existing integrations and edit their details from here.)
- Choose the type of service you want to include in your integration. You can get API access to several Adobe services or subscribe to real-time events. An integration can access multiple services and event sources. Simply perform these steps for each service or event you want to add to your integration.
-
Select Access an API to create an integration that will access an Adobe product API or service, you will have an opportunity to subscribe to additional services and events once you have created the integration.
-
Choose the service or event source that you would like to add to your integration. APIs and products available through Adobe I/O are typically listed by cloud.
- The configuration page lets you provide all of the required details for a new integration, or add new information to update an existing integration. On this page:
Integration Details | |
---|---|
Name |
Enter a unique name to easily identify your integration |
Description |
Provide a brief description about this integration. If you have multiple applications or access multiple services, you can use these properties to better organize your integrations. |
Platform |
Select a platform on which the integration is intended to be used: iOS ,Android ,Web |
Default Redirect URI |
After a user successfully authorizes an application, the authorization server will redirect the user back to the application with either an authorization code in the URL. Because the redirect URL will contain sensitive information, it is critical that the service doesn’t redirect the user to arbitrary locations. (HTTPS required) |
Redirect URI pattern |
A comma seperated list of URI patterns, to validate additional custom redirect uri passed along with Authorization request. (HTTPS required) e.g. https://www\\.myapp\\.com will allow redirect uris like https://www.myapp.com/OAuth/callback |
-
Tip: Give your integrations accurate and descriptive names. Integrations are shared with developers within your organization, so choose a name that is clear and easily understood. Generic names like My Test App are discouraged.
-
Click Create integration.
-
When creation is confirmed, visit the overview section for your new integration. The overview section contains the newly generated API Key, and allows you to subscribe to additional services or events.
- Copy your integration API Key and replace it with
myAPIKey
in below request.
curl 'https://stock.adobe.io/Rest/Media/1/Search/Files?locale=en_US%26search_parameters%5Bwords%5D=kittens '
-H 'x-api-key:myAPIKey'
-H 'x-product:myTestApp1.0'
- Open Postman and go to
Import
->Paste Raw Text
and paste the curl command.
- Click Send. You will receive a successful response. Note that you did not need an access token for making a successful request using API Key integration.