Overview

This system is catalog top-level because api-v1 is not owned by a single domain. It is the HTTP machinery other domains call.

api-v1

Status: active Airtable-backed implementation (MVP carrier).

• Primary backend for current product and marketplace workflows.
• Formal route documentation, domain discovery, and day-to-day development.
• Not deprecated — migration to api-v2 is planned after the MVP, not during active domain build-out.
• OpenAPI: EventCatalog embeds the generated spec; published JSON: /openapi/api-v1.json.

api-v2

Status: longer-term Prisma/Postgres target (CRM and selected modules live here today).

• Newer backend with DDD/hex modules for domains that have already moved.
• Target destination for remaining api-v1 capabilities after the MVP.
• OpenAPI: EventCatalog embeds the generated spec; published JSON: /openapi/api-v2.json.

Guiding rule

EventCatalog is the system catalog. OpenAPI is the API contract. Prefer documenting and extending api-v1 for active MVP work. Document api-v2 for modules that already live there and for planned migration surfaces — do not treat api-v1 as legacy.

Open question

Part of api-v2 is a sandboxed Postgres read path so the client can avoid Airtable rate limits. That is not the v2 migration. Do not invent a clean split between “MVP Airtable API” and “future Prisma API” until that read path is modelled separately.

Fixing that split is a separate task.