All topics
โš™๏ธ

API Design

Standards for describing, building, and contracting APIs: OpenAPI, GraphQL, gRPC/protobuf, AsyncAPI, JSON Schema.

API DesignData Formats
1
Must Know
5
Should Know
0
Niche

Must Know

1 spec
OpenAPI 3.1.0RFCMust Know

OpenAPI 3.1

OpenAPI is the de-facto standard for API documentation, code generation, mock servers, and contract testing. Most APIs you build should have an OpenAPI spec.

ProductAPI DesignAPI Design
Details

Should Know

5 specs
JSON Schema Draft 2020-12RFCShould Know

JSON Schema

JSON Schema is the standard way to document and validate API request/response shapes. OpenAPI 3.1 fully adopts it. Know it if you design APIs.

ProductAPI DesignData Formats
Details
GraphQL June 2018GraphQLShould Know

GraphQL

GraphQL solves over-fetching and under-fetching in complex UIs. If your frontend needs flexible, composable data queries across multiple entity types, GraphQL is the tool.

ProductAPI DesignAPI Design
Details
gRPC over HTTP/2gRPCShould Know

gRPC

gRPC is the dominant service-to-service RPC in polyglot microservices. Smaller payloads and faster than JSON/REST for high-throughput internal APIs.

ProductAPI DesignAPI Design
Details
proto3gRPCShould Know

Protobuf

Protobuf is the wire format for gRPC and many high-performance internal APIs. Schemas are also used for event/message contracts in Kafka/pubsub systems.

ProductAPI DesignAPI Design
Details
AsyncAPI 3.0AsyncAPIShould Know

AsyncAPI

If you have event-driven systems (Kafka, RabbitMQ, WebSocket APIs, IoT), AsyncAPI is the description format. Analogous to OpenAPI for async what OpenAPI is for REST.

ProductAPI DesignAPI Design
Details