Week 5 – API Design

Goal

Define your airline backend's external API contract and expose the documentation from your backend service at /docs. Use OpenAPI for the contract.

Required Deliverables

1. Publish OpenAPI documentation for your backend at /docs.
2. Define only the external-facing APIs that other systems would use to shop for flights, view flight details, and perform any other airline-facing operations you choose to support.
3. Create a full distributed system diagram in Excalidraw showing the major services, queues, databases, and integrations in your team architecture.

API Scope

Each team has flexibility in the exact request/response shape. You are free to define your own interface and response model.

Minimum Expectations

• Your backend service exposes /docs successfully.
• The OpenAPI contract is valid and readable.
• The contract describes external-facing shopping APIs.
• The Excalidraw diagram covers the full distributed system.

Suggested Endpoints

These are examples only; you may define your own shape.

• GET /flights/search
• GET /flights/{id}
• POST /bookings

Grading Breakdown