







When writing APIs, REST (short for representational state transfer) is considered the standard. And yet, REST itself isn’t actually a …
A brief history of Web APIs
A quick summary of Web APIs, both prior to and subsequent to the REST revolution

How a RESTful API server reacts to requests
Learn how to properly design RESTful APIs communication with clients, accounting for request structure, authentication, and caching.

「WebAPI 設計のベストプラクティス」に対する所感 - Qiita
「翻訳: WebAPI 設計のベストプラクティス」を読んで色々と思うところがあったので書きました。 上記の記事は訳文でありますので、正しくは「Best Practices for Designing a Pragmatic RESTful API」に対する所感と述べた方が良...

Progressive Enhancement with the WordPress REST API – Pre-Thought Listen
In a REST API discussion today, we discussed the future of the REST API. Something I touched upon briefly in that meeting is the concept of progressive enhancement with the REST API. Since this topic hasn’t been brought up much previously, I want to elaborate on how progressive enhancement works.
Introducing the HyperMap Stack
A brief introduction to HyperMap, a new RESTful API stack which supports client-side code execution
APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
I was exchanging emails with someone regarding API design considerations at their large institutions today, and where they could find healthy patterns for AP...
Developing The Language We Need To Communicate Throughout The API Lifecycle
We are still in the infancy of the API economy, and now with barely 14 years of evolving web API design, we are only just now developing the languages we wil...
翻訳: WebAPI 設計のベストプラクティス - Qiita
これは Enchant の開発者である Vinay Sahni さんが書いた記事「Best Practices for Designing a Pragmatic RESTful API」1を、ご本人の許可を得て翻訳したものです。 RESTful な WebAPI を設計し...

The Rise and Rise of JSON
JSON has taken over the world. Today, when any two applications communicate with each other across the internet, odds are they do so using JSON. It has been adopted by all the big players: Of the ten most popular web APIs, a list consisting mostly of APIs offered by major companies like Google, Facebook, and Twitter, only one API exposes data in XML rather than JSON.1 Twitter, to take an illustrative example from that list, supported XML until 2013, when it released a new version of its API that dropped XML in favor of using JSON exclusively. JSON has also been widely adopted by the programming rank and file: According to Stack Overflow, a question and answer site for programmers, more questions are now asked about JSON than about any other data interchange format.2

</> htmx ~ Hypermedia APIs vs. Data APIs
In this essay, Carson Gross explores the fundamental differences between hypermedia APIs and data APIs, He explains how hypermedia APIs, which return HTML over HTTP, can embrace frequent changes due to their self-describing nature, while data APIs require more stability and versioning to avoid breaking client code. Carson argues that these distinct characteristics should inform different design approaches for each type of API.
GraphQL vs REST: Everything You Need To Know
Not sure how GraphQL and REST differ? We explain everything you need to know, from how they each work to which you should be using.

What Is APIs.json? And What Is Next For the API Discovery Format?
As part of a renewed focus on the API discovery definition format APIs.json, I wanted to revisit the propsed machine readable API discovery specification, an...

HTTP Semantics
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.
The unifying REST API for all the OpenCitations Indexes
Old Version of OpenCitations INDEX API
Hypermedia APIs
Introduction to the DataCite REST API
About the DataCite REST API The DataCite REST API enables retrieval, creation, and update of DataCite DOI metadata records and account information. The API is generally RESTful and returns results in JSON (following the JSON:API specification). REST API Reference 📘 Access the REST API Reference to ...
.%20REST%20API%20Reference%20%F0%9F%93%98%20Access%20the%20REST%20API%20Reference%20to%20...&logoUrl=https%3A%2F%2Ffiles.readme.io%2Ffb9347b-small-DataCite-Logo_secondary.png&color=%23243B54&variant=light)