As with any industry, the web API space faces different approaches to standardization. Not least of which are the differences between how API providers choose to define their APIs in a machine readable way with API specifications and description languages.
API definitions have emerged as ways to annotate API functionalities, and there are still many out there catering to varying web service architectures. Read more
Whether you’re a startup developing your first API or an established player in the API economy, the truth is becoming steadily more apparent; providing quality API documentation is vital to the success of an API initiative. API documentation is an important part of the product offering, delivering affordances to the developer community to help them understand exactly what an API offers and how to use it. Read more
The most common API definition languages we spot in the wild are Swagger / OpenAPI Spec, RAML and API Blueprint. All three let you define your endpoints, your resources, your query or path parameters, your headers, status codes, security schemes, and more. Read more
As the API community starts a new year, we do so with an increasingly wide choice of API description formats at our disposal. However, a development late last year promises to alter this landscape by introducing an initiative aimed at standardizing how APIs are described. Read more