I have a lot of work to do profiling APIs using APIs.json. I am interested in producing as complete an accurate APIs.json for an API provider as I possibly can. When it comes to profiling providers like Amazon Web Services (AWS), this means there are over 350 individual APIs. It isn’t enough that I have a name, description, and tags for each API, but I also want OpenAPI and other properties defined for each one. AWS is pretty formulaic in how they approach their operations, but there is some nuance to each one that takes a balanced approach to profiling.

API Evangelist's publication is a resource for developers, architects, and technology leaders seeking to understand the importance of APIs in modern software development. Through articles, case studies, and industry insights, API Evangelist offers insights into API design best practices, API management strategies, and API-driven business models. Readers can learn about RESTful API principles, GraphQL implementations, and microservices architecture to build scalable and interoperable software systems.

API Evangelist

The author discusses their approach to profiling APIs using APIs.json, including the tools and processes they have developed. They aim to strike a balance between hand-curation and automation, and are working on automating the discovery of new APIs.

Streamlining the Profiling of APIs Using APIs.jsons

<p>Having a list of APIs in one place sounds great in theory, but I feel like it’s all too easy to simply google-search what you need, especially when most people are using popular APIs. Unless you’re able to curate APIs which don’t or can’t get much exposure, I don’t think this will be very useful.</p>
