APIs · Intermediate · Hybrid
REST Contract Design Studio
Model resources, pagination, and idempotency keys with reviewable OpenAPI drafts.
Participants bring a messy endpoint family; we refactor it toward predictable contracts. Expect sharp questions about nouns, verbs, and what clients actually need.
Duration: 6 weeks
Tuition (informational): 6,200,000 VND
Final quotes come from admissions. See Money-Back Policy for eligibility.
What ships in the syllabus
- Resource naming critiques with real-world counterexamples
- Pagination strategies: cursor vs offset tradeoffs
- Idempotency-Key walkthrough for write-heavy flows
- OpenAPI lint rules wired into CI
- Consumer-driven fixture tables
- Breaking change playbook
- Office hours with API reviewer
Outcomes we actually assess
- Publish a reviewed OpenAPI document for one domain
- Draft a migration note for a breaking field rename
- Facilitate a 30-minute design review using a rubric we provide
Minh Vo
API reviewer for payment integrations; publishes internal RFC templates.
FAQ — including what we skip
Is Postman required?
We standardize on Bruno collections for cohort consistency; Postman exports are supported during week one only.
Will you write legal terms for my API?
No legal drafting—only technical contract language and examples.
Limitation on team size?
Pair tickets assume two engineers; larger teams should split domains before joining.
Experience notes
“The idempotency module referenced our invoicing edge case—not a toy cart.”
“Anonymous feedback: pacing on HATEOAS was fast, but office hours cleared it.”