As I was profiling APIs on my list of APIs I found myself profiling Adobe. I am moving through the list of companies alphabetically, so you can see how far along I am. Anyways, like any other large company I need to make a decision about how I am going to manage the profiling of different API products and lines of business. Companies like Amazon, Google, Azure, and Adobe have large numbers of APIs and I always know I will need to have some sort of plan for documenting everything that is going on. With Adobe, I am going to track everything in a single GitHub repository, but will be working to create separate API definitions (OpenAPI and Postman collections) for each of the individual APIs being offered.
To provide some context, it helps to understand why I profile APIs in the first place. As the API Evangelist I review public API operations studying how API providers are doing what they do. I then aggregate the “building blocks” of their public operations into a master set of reserarch that I use to drive my storytelling and API strategy workshops. So, with the Adobe APIs I’m not looking to review their API operations as much as I am looking to understand how they operate, and develop an understanding of how far along they are in their enterprise API journey. As with any profiling of a company, I begin by Googling their name pus API, but then dive as deep as I can into the details of what I find with each click.
When you Google Adobe APIs you get this main landing page with the tagline, “APIs and SDKs for all Adobe products – create mobile, web and desktop apps”. You can tell Adobe is working hard to bring together their APIs under one big tent, with the following main areas to support developers:
- Landing Page - Adobe API landing page.
- Authentication - Overview of authentication.
- Open Source - An open source page.
- Blog - Their tech blog for their APIs.
- GitHub - A dedicated GitHub account.
- Twitter - A dedicated Twitter account.
- YouTube - A dedicated YouTube account.
- Support - The support for API developers.
- Release Notes - Release notes for APIs.
- Privacy Policy - The privacy policy.
- Terms of Use - The terms of use.
- Cookies - The cookies policy.
These building blocks provides the basis for their API operations, providing a single landing page for brining everything together, and help folks find what they are looking for when it comes to APIs for all of the Adobe products. When listing out their products Adobe breaks them into three distinct categories:
- Creative Cloud
- Document Cloud
- Experience Cloud
- Adobe Experience Platform
I worked my way through each of the Adobe products, there is a mix of available resources for each of their lines of business, but I am purely looking specific HTP API signals that I can profile and add to my index of APIs. While looking through each of these area I’m looking for the elements that help me quantify the value being offered by each of the Adobe APIs. While looking through the Adobe I/O program I can ame across 15 APIs, that had enough meat on the bones for me to profile and add to my index.
Adobe Launch
