Learning path

API design for backend developers

A curated path through API style, REST checklists, OpenAPI contracts, schema boundaries, authentication, scopes, HTTP behavior, error contracts, pagination, retries, gateways, webhooks, and JSON tooling for maintainable backend APIs.

10 guides and tools

Authentication and access

Protect APIs with authentication choices, cookies vs tokens, API keys, OAuth scopes, service credentials, gateways, and clear auth failures.

Start here

Pillar guides

These articles are the strongest entry points into the API design cluster.

Related tools

Local tools for API design work

Use these browser-based tools while reviewing payloads, response contracts, IDs, and logs.

Available tool

HTTP Status Code Lookup

Search common HTTP status codes locally in your browser with REST API usage notes, retry guidance, and backend examples.

Open tool

Available tool

JSON Schema Generator

Generate a starter JSON Schema from example JSON locally in your browser for API contracts, validation, tests, and documentation.

Open tool

Available tool

JSONPath Tester

Test common JSONPath expressions against JSON locally in your browser for API debugging, fixtures, logs, and documentation.

Open tool

Available tool

JSON Pointer Resolver

Resolve RFC 6901 JSON Pointers against JSON locally in your browser for OpenAPI, JSON Schema, JSON Patch, and API debugging.

Open tool

Available tool

UUID Generator

Generate UUID v4 values locally in your browser for request IDs, idempotency keys, database records, and test data.

Open tool

Available tool

Unix Timestamp Converter

Convert Unix timestamps to UTC and local dates, or convert date strings to seconds and milliseconds locally in your browser.

Open tool

How to study

Design for clients, failures, and change.

Strong API design is not only endpoint naming. It is the contract clients rely on: request shape, response shape, schemas, status codes, retry behavior, pagination metadata, versioning, and integration failure modes.

Start with API style and response behavior, then move into reliability topics such as idempotency, rate limiting, retries, and webhook delivery.

For adjacent backend architecture topics, browse the System Design Learning Path.

FAQ

API design learning questions

What should I learn first in API design?

Start with REST vs RPC, a REST API design checklist, OpenAPI schemas, HTTP status codes, stable error responses, versioning, pagination, and idempotency. Those topics shape most long-lived backend APIs.

Is API design only about REST?

No. REST is common for public HTTP APIs, but RPC, gRPC, event-driven APIs, and webhooks are also useful depending on the workflow and clients.

Which API design mistakes cause the most production pain?

Unstable response shapes, unclear error codes, unsafe retries, missing idempotency, weak pagination rules, and breaking changes without migration plans are common sources of pain.

How do the API tools fit this learning path?

The tools help inspect status codes, generate schema or TypeScript drafts, resolve JSON paths, create request IDs, and debug timestamps while designing or reviewing APIs.