Design APIs that last and documents that work
Day 1
REST Design Principles & OpenAPI Specification
- REST constraints and what actually makes an API RESTful
- Resource modeling: identifying nouns, collection vs singleton, sub-resources
- HTTP methods: GET, POST, PUT, PATCH, DELETE — correct semantics
- Status codes: 2xx, 4xx, 5xx — and the ones teams always get wrong
- Request and response design: consistent naming, field selection
- Error format: RFC 9457 Problem Details — machine-readable, actionable
- Versioning strategies: URI, header, content negotiation — trade-offs
- Pagination: offset, cursor, keyset — choosing the right pattern
- OpenAPI 3.1: describing paths, parameters, request bodies, responses
- Schema design: reuse with $ref, oneOf/anyOf for polymorphism
- Springdoc with Spring Boot: auto-generating and customizing the spec
- API-first workflow: generate server stubs and client SDKs from the spec
- Spectral linting: enforcing API style guides automatically
What your team walks away with
API designers who build contracts that are consistent, evolvable, and easy to integrate against — with an OpenAPI spec that serves as living documentation.
- Design REST APIs with correct resource modeling and HTTP semantics
- Write OpenAPI 3.1 specs that generate accurate documentation and client SDKs
- Apply RFC 9457 Problem Details for consistent, actionable error responses
- Enforce API style consistency with Spectral linting in CI
Book the REST API Design training
A focused one-day course — works well standalone or as part of a backend API development track with Spring Boot.
Get in touch