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.
  1. 01Qué es una API y qué es un buen diseño8 LESSONS
    1. Module introduction: Mercado's API as a public contract
    2. An API is a contract
    3. Consumer-oriented, not the DB table
    4. Resources, not actions
    5. Consistency and the principle of least surprise
    6. The cost of breaking the contract
    7. The Mercado API: good and bad examples
    8. Mini-project: redesign an endpoint that leaks the schema
  2. 02REST bien hecho8 LESSONS
    1. Module introduction: the semantics HTTP already gave you
    2. Resources and collections
    3. The verbs: safe and idempotent
    4. PUT, PATCH, and DELETE
    5. Status codes 2xx
    6. Status codes 4xx and 5xx
    7. Clean URLs
    8. Project: model Mercado's REST endpoints
  3. 03Diseño de peticiones y respuestas8 LESSONS
    1. Module introduction: designing what comes in and what goes out
    2. Pagination: why cursor beats offset
    3. Filtering and sorting
    4. Field selection: sparse fieldsets
    5. Envelopes vs bare resource
    6. Dates and times: ISO 8601 in UTC
    7. Money: integer cents, never float
    8. Project: design Mercado's `GET /products` responses
  4. 04Errores y códigos de estado8 LESSONS
    1. Module introduction: the error is part of the contract
    2. Why an error contract
    3. `problem+json`: the standard format (RFC 9457)
    4. 400 vs 422 vs 409: which code for which failure
    5. The other codes: 401, 403, 404, 410, 429
    6. Actionable errors: which field and how to fix it
    7. Idempotency of POST with Idempotency-Key
    8. Project: Mercado's error contract
  5. 05Versionado y evolución8 LESSONS
    1. Module introduction: the promise you can no longer break
    2. Why evolving breaks
    3. Additive vs destructive changes
    4. Versioning in the URL vs in a header
    5. The tolerant reader
    6. Deprecation with Sunset
    7. Does this change break? The checklist
    8. Project: evolve Mercado's Product without breaking the old consumer
  6. 06Contratos, schemas y documentación8 LESSONS
    1. Module introduction: the contract that can be read without you
    2. Why an explicit contract
    3. OpenAPI: describing the API in a file
    4. JSON Schema: the shape of data
    5. Contract-first: the contract before the code
    6. Validating the request against the schema
    7. Documentation as part of the contract
    8. Project: the OpenAPI + JSON Schema of a Mercado endpoint
  7. 07Más allá de REST — gRPC y GraphQL8 LESSONS
    1. Module introduction: when the default stops being free
    2. When REST isn't enough
    3. gRPC and protobuf: the contract that generates code
    4. When to choose gRPC
    5. GraphQL and the exact request
    6. GraphQL's N+1 problem
    7. The choice matrix: REST, gRPC, GraphQL
    8. Project: choose the protocol for each Mercado boundary
  8. 08Proyecto — diseña la API de Catalog de Mercado8 LESSONS
    1. Module introduction: the API as a contract, in a single design
    2. Resources and endpoints: the complete surface
    3. Cursor pagination and filtering
    4. The error contract and idempotency
    5. The JSON Schema and the docs as contract
    6. The versioning plan and a change that doesn't break
    7. The protocol decision per boundary
    8. 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!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab