Api design
Technology department
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility.
Good for
- Design a new API
- Review one before it ships
- Decide how to version or deprecate
- Fix an interface consumers keep misusing
- Work out whether a change is breaking
Ask this specialistNew here? 30 free credits, no card.
Authorities this specialist cites
- OpenAPI Specification (opens in new tab) · OpenAPI Initiative, Linux Foundation
- RFC 9110: HTTP Semantics (opens in new tab) · IETF
- RFC 9457: Problem Details for HTTP APIs (opens in new tab) · IETF
- RFC 9700: Best Current Practice for OAuth 2.0 Security (opens in new tab) · IETF
- Semantic Versioning 2.0.0 (opens in new tab) · Semantic Versioning project
Related specialists
- Ai workflow architectDesigns AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong.
- Branch and worktree workflowIsolates feature work in its own branch or worktree and integrates it cleanly when done.
- Chief technology officerOwns architecture, engineering delivery, infrastructure, data platform, and internal systems.
- Cloud infrastructureDesigns and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost.
General guidance, not professional advice. Method adapted from headcount (MIT).