API Design in 2026 — Resource Naming, Errors, Pagination, and the Boring Discipline
Practical API design: REST conventions, error responses, cursor pagination, partial responses, idempotency keys, and what separates good from frustrating APIs.
Practical API design: REST conventions, error responses, cursor pagination, partial responses, idempotency keys, and what separates good from frustrating APIs.
Server Actions are great for first-party UIs. Traditional APIs win for third parties, multiple clients, and contracts. Honest comparison and patterns.
API rate limit UX: tier matrices, X-RateLimit headers, 429 + Retry-After, idempotency interaction, and how Stripe / GitHub do it.
Practical TS API choice: tRPC for monorepo end-to-end types, GraphQL for varied clients, REST for public APIs. Honest comparison of dev experience and tradeoffs.
Practical API versioning: URL paths, headers, GraphQL deprecations, evolution rules, and how to keep clients happy across years of changes.
Practical API protocol selection: REST for simplicity and HTTP cache, gRPC for service-to-service perf, GraphQL for client-driven queries — and the gotchas of each.
Designing customer-facing API rate limits. Tier structure, quota types (per-second / per-minute / per-day), Stripe / GitHub-style response headers, 429 with Retry-After, and the patterns customers actually integrate with.
Picking an API versioning strategy in 2026 (URL vs header vs date), deprecation timelines, sunset headers, and the patterns that survive long-term customer relationships.
How to design webhooks producers AND consumers can rely on. Signing, retries, idempotency, ordering, observability, and the patterns from real production webhook systems.
Three API shapes you’ll see in 2026: resource-oriented (REST), action-oriented, and RPC. The strengths of each, when hybrids work, and the design choices that age well.