Skip to content
Maduka Okwuchukwu
All work

Backend · REST API

Cookeaze API

The Django REST backend behind Cookeaze — one documented API serving the iOS, Android and web apps.

Role
Backend engineer — design, build and deployment
Platform
API
Stack
Python, Django, Django REST Framework, PostgreSQL, OpenAPI / Swagger
api.cookeaze.app/api/swagger
Cookeaze API Swagger documentation

Overview

The Cookeaze API is the single source of truth for the whole product: recipes, meal plans, grocery lists, creators, memberships, payments and user data.

It's a versioned REST API built with Django REST Framework and documented with OpenAPI, so the Flutter app and the Next.js web app share exactly the same contract.

Who it's for

The Cookeaze mobile and web clients, and any future integrations.

Key features

  • Versioned REST API (v1) over HTTPS
  • Interactive OpenAPI / Swagger documentation
  • Token-based authentication and per-user permissions
  • Resources for recipes, meal plans, grocery lists and creators
  • Addresses with full CRUD and default-address handling
  • Memberships and exclusive-content entitlements
  • Serves iOS, Android and web from one codebase

Screenshots

api.cookeaze.app/api/swagger
Cookeaze API Swagger documentation

Challenges

  1. 01

    One contract for every client

    Mobile and web release on different schedules. A versioned, documented API lets each client move at its own pace without breaking the other.

  2. 02

    Access rules on the server

    Premium recipes and memberships are enforced in the API, not the UI, so every client gets the same answer to “can this user open this?”.

See it live