API Development
API studio: versioning, contracts, and tests
Design-first HTTP APIs with Laravel resources, schema checks, and contract tests.
You sketch payloads, codify them with validation rules, and keep consumers from guessing edge cases. We practice deprecating fields without breaking mobile clients.
Included focus areas
- Versioned routes and sunset headers without drama
- API resources, optional fields, and sparse responses
- Pest suites around happy and unhappy paths
- Rate limiting stories for public vs internal tokens
- Postman collections checked into the repo
- OpenAPI notes for partner teams
- Observability: correlation IDs through middleware
Outcomes
- Publish a versioned API with documented change notes
- Ship failing tests before fixes when regressions appear
- Walk stakeholders through payload diffs calmly
Noah Kim
Program director; ships internal platforms for product squads across Seoul.
Questions
GraphQL included?
REST-first. We discuss when GraphQL fits, but exercises stay JSON HTTP.
Do I need Postman experience?
No; we share starter environments on day one.
Cancellation window?
See Cancellation Policy for workshop-specific dates.
Experience notes
-
Contract tests caught a field rename I would have shipped on a Friday. The versioning lecture felt dry until the live rollback exercise.
Sora · Mobile engineer · 4/5 · Google
-
We mirrored a messy legacy payload and still kept tests readable. Rare in short courses.
Eun · Retail internal tools