Authenticate and access Experience Platform APIs

Transcript

Alright, after we’ve generated our access token, we can begin interacting with Adobe IO APIs. In this video, I interact with experienced platform APIs, using Adobe-provided Postman collections. To access these collections, head over to the experience-platform-postman-samples GitHub repository, navigate into APIs, Experience Platform, and there’s a Postman collection for each of the APIs available. For this video, I load a single collection for the Schema Registry API.

Once we’ve downloaded all the collections that we want to use, let’s head back to Postman, select import, and load all the Postman collection files.

As you can see, we have our Schema Registry API collection, and within this are a number of folders, and within each folder, are the HTTP requests we can make to interact with the API. Let’s keep this simple, and interact with the stats API.

So we can simply open this up, we can look at the headers, which are mapped to the environment variables, which are provided by the Adobe API environment export, as well as the access token, which we obtained from the Adobe IO access token generation Postman collection. Alright, so let’s try this out. We just hit send, to execute the API command, and there you go, we’ve successfully interacted with experienced platforms, a Schema Registry API, using Postman.

Transcript

In this video, we’ll show you how a system admin can add a developer for Adobe Experience Platform using Adobe Admin Console. We’ll also show you how to add a developer’s API credentials to a role in the platform interface to grant access to features and sandboxes for the API integrations the developer will build. Experience Platform’s OpenAPI ecosystem allows developers to directly integrate platform capabilities into their own applications. In order to gain access to these APIs, users must be added as developers for Experience Platform through Adobe Admin Console. Once access has been granted, developers can generate credentials for Experience Platform APIs and use those credentials to create integrations with multiple applications. To add a new developer, you must be a system administrator for your organization. Start by logging into Adobe Admin Console, then navigate to the Products tab. Next, select Experience Platform, and here we see the default product profile called AEP Default All Users. So we’ll click into it. From here, we’ll select the Developers tab, then click Add Developer. In the dialog that appears, add the email addresses of the users that you want to add as developers for Experience Platform. If the email is associated with an Adobe ID or a Federated ID, further details about the user are auto-populated. If the email is not associated with Adobe Account, we’re given the option to manually enter their details instead. From here, you can scroll down to continue adding more developers if you wish. And once you’re happy with your selections, select Save to apply them. And that’s the first step done. These users now have developer access to platform and can generate API credentials using Adobe Developer Console. However, in order for those API credentials to actually provide access to specific platform capabilities, we need to perform the second step in the Experience Platform interface. Once a developer has generated their API credentials in Developer Console, navigate to the Permissions tab in the Platform interface. In Platform, we grant API access to features using a similar workflow to adding new users. In other words, we need to add the developer’s API credentials to a role, which provides access to a certain set of platform features and sandboxes. Clicking into one of the existing roles, select the API Credentials tab, and then select Add API Credentials. Here we have a list of credentials to choose from, and if the developer generated their credentials correctly, they should appear here. To narrow down the list, ask the developer for the technical account email that was generated as part of their credentials. Copying this value into the search box, we can locate the exact set of credentials that we want to add to this role. So, we’ll select it and then hit Save, and now these credentials have been added. When the developer uses these credentials in their API integration, they can use all of the platform features and sandboxes that this role grants access to. As a final step, we may also want to add the developer as a user under this same role, so they can also access the Platform interface to test and verify their API integrations. Heading over to the Users tab, select Add Users and select the developer from the list before hitting Save. If you don’t see them listed as a user here, be sure to add them as a user in Admin Console first. And that’s it! The newly added developer can now start building API integrations using their generated credentials. For details on how to leverage platform APIs in your code, please refer to the documentation. Thanks for watching.