BEGINNER · 8 MODULES · 64 LESSONS
API Design and Integration
Design APIs other systems can use without surprises: clear resources, useful errors, solid pagination, and changes that never break existing consumers.
- For you if
- You build backend endpoints and want to stop improvising contracts that break at the first change.
- By the end
- You'll know how to version an API, make requests idempotent, document it with OpenAPI, and decide when gRPC or GraphQL fits.
- You need
- Basic Python and HTTP, and at least one endpoint you've built, even a simple one.

Curriculum
01Qué es una API y qué es un buen diseño
- Module introduction: Mercado's API as a public contract
- An API is a contract
- Consumer-oriented, not the DB table
- Resources, not actions
- Consistency and the principle of least surprise
- The cost of breaking the contract
- The Mercado API: good and bad examples
- Mini-project: redesign an endpoint that leaks the schema
03Diseño de peticiones y respuestas
04Errores y códigos de estado
- Module introduction: the error is part of the contract
- Why an error contract
- `problem+json`: the standard format (RFC 9457)
- 400 vs 422 vs 409: which code for which failure
- The other codes: 401, 403, 404, 410, 429
- Actionable errors: which field and how to fix it
- Idempotency of POST with Idempotency-Key
- Project: Mercado's error contract
05Versionado y evolución
06Contratos, schemas y documentación
- Module introduction: the contract that can be read without you
- Why an explicit contract
- OpenAPI: describing the API in a file
- JSON Schema: the shape of data
- Contract-first: the contract before the code
- Validating the request against the schema
- Documentation as part of the contract
- Project: the OpenAPI + JSON Schema of a Mercado endpoint
07Más allá de REST — gRPC y GraphQL
08Proyecto — diseña la API de Catalog de Mercado
- Module introduction: the API as a contract, in a single design
- Resources and endpoints: the complete surface
- Cursor pagination and filtering
- The error contract and idempotency
- The JSON Schema and the docs as contract
- The versioning plan and a change that doesn't break
- The protocol decision per boundary
- Project: design and execute the Catalog+Orders API
Reviews
What students say
These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.
No approved reviews yet.
Be the first to share your experience!