API Evangelist is a site dedicated to the technology, business, and politics of APIs. Beginning as a research site studying many different types of APIs, and then evolving towards developing an understanding of the common building blocks API providers are using across the API lifecycle. You can find research across 100 stops along the API lifecycle below, as well as the ability to browse for APIs, and access other resources like industry guides, blueprints, landscape analysis, as well as a regular storytelling from across the API sector.

COVID-19 Data and Information

A Proof of Concept API Service Tier

The Official Cloudflare API Postman Collection

I have a lot of information regarding APIs on my network of sites, but I'm always trying to make sure I have a sufficient amount of introductory and getting started information for people who are just learning what an API is, and what is possible.

I have compile some introductory information to help walk you through the concept of an API, and how they have been expanding over the last 15 years across all the online services you have become familiar with on the web and mobile phone.

• Getting Started With APIs

The history of APIs goes back 50 years, but the history of web APIs is approach 20 years. Some of this history is already set in stone, but other parts of it is still being understand in the moment. Over a decade of trying to understand what is happening across the sectory I have been gathering details to use in my history of APIs storytelling.

I've compiled a short history of web APIs for public browsing, but I also have a more detailed history that I'm working on publishing as a guide, helping better walk through the history of APIs and how it has impacted our personal and professional lives. Once done, I will publish the guide here on the blog, but until then, enjoy my short snapshot of the history of APIs as we know it.

• The History Of APIs

The types of APIs we are keeping an eye on. Breaking APIs down into a variety of topics, which we are constantly re-discovering, refining, and reworking to better reflects what is hapening across the API sector, accessible via separate API Evangelist network microsites.

Almost 100 stops along a series of interconnecting API lifecycles employed by API providers, consumers, and tooling developers--providing a comprehensive look at the infrastructure API providers are using to define, deliver, scale, and distribute their API operations.

This is a guide to the world of API definitions. Introducing you to what the machine and human readable schema and API specification formats are used for when it comes to defining API-driven capabilities. Formats like JSON Schema, OpenAPI, AsyncAPI, and Postman Collections are changing how we define our APIs, and then use definitions to engage with developers throughout the API life cycle.

The API definitions guide is the result of almost 10 years of research and participation in the evolution of API definitions as part of community development, conferences, and the API efforts behind the specifications themselves. I've distilled my research on API definitions down into a short guide that business as well as technical individuals can follow. Providing a single guide to the impact that API definitions are making across the sector, empowering both API providers and consumers when it comes to putting APIs to work in web, mobile, and device applications.

This is an API blueprint for the Twilio ecosystem. Providing an easy to follow breakdown of the building blocks Twilio uses to operate its API platform, and achieve success with its API community. Providing a checklist that other API providers can consider when crafting their own API strategy, and learning from the pioneers and leaders who have helped define the world of APIs.

The Twilio API blueprint takes you for a stroll through the different areas of the Twilio API ecosystem, learning more about the company, it's products, services, tooling, and other elements of it's operations. As we learn about Twilio's approach to delivering APIs and engaging with it's API community we try and explain why their approach matters even if you aren't intending on being a communication API like Twilio, and that there plenty of lessons for API providers of all types to apply this blueprint within their own operations.

While developing a WebRTC application may not be the easiest web application you’ll be developing, scaling it properly to a large number of users is a lot more challenging.

This eBook outlines some of the best practices in the industry that companies are using to scale their own WebRTC deployments. If you plan on launching a production service with WebRTC, and want it to scale successfully, then the insights found in this eBook will be invaluable to you.

About The Author
Tsahi Levent-Levi is a developer at heart. He has been working in the telecom and VoIP/UC industries of the past 20 years (and counting) in various roles: from a developer, to project manager, product manager and CTO. Most of that time, Tsahi was dealing with signaling and media products that were licensed to other developers who built their own products with them. This gives him a broad view of the market and an understanding of the challenges and opportunities that exist in the domain of VoIP.

This is an executive summary of a single stop along the API lifecycle to think about when planning your own API strategy, but this guide is dedicated to understanding how different geographical regions are influencing how we think about APIs. This isn't something that is unique to APIs, and the multi-regional availability of applications, infrastructure, and APIs is born out of the cloud evolution--with the big three (AWS, Google, and Azure) dominating the landscape, and who are rolling out new availbility regions at a break neck pace. Making it very realistic and cost effective to deliver API infrastructure in a variety geographic regions.

To help API providers understand the growing importance of how geographic regions can be leveraged, I distilled down my API regions research into the follow areas, resulting in this guide that is full of considerations to share with your team when thinking about how to go global with your API operatons.