Content API reference

Every tenant is one document in the sites collection. Its key field (the siteKey) identifies the tenant; consumer apps authenticate with the site's API key, which resolves to this document.

All other content documents carry a siteId field referencing the owning sites document. companies and siteSettings are one-per-site; legalTexts is one-per-document-key; services, products, caseStudies, locations and values are one-per-slug within a site; assets are one-per-pathname.

All documents also carry MongoDB _id, createdAt and updatedAt fields managed by the database layer; they are omitted from the tables below.

The platform owns design-agnostic business data only: business identity and contacts, opening hours, the services performed, the products sold, the case studies published, locations, company values, and the legal documents the client maintains. Every client website has its own bespoke design, so page structure, layout, section copy and metadata (band headings, stat figures, call-to-action labels, intro blocks) live in the client site's own repository and are deliberately absent from this contract.

Each resource maps to one collection: settings to companies, services/products/caseStudies/locations/values to their per-slug collections (array position stored in each document's order field), and legal to one legalTexts document per document key. Platform-only data never leaves: companies.availability is the schedule designer's working data (client sites read the schedule lines derived from it) and the whole siteSettings document holds backoffice preferences.

A service is work scoped per job and carries no price; a product is something sold at a stated price, stored as an amount plus its currency and billing period so each website can format it in its own style; a case study is work already delivered, told as problem, solution and results.

Resource responses omit siteId and every platform-only field, and they are fully defaulted: missing strings come back as empty strings and missing arrays as empty arrays. A site with no content yet returns valid empty resources rather than an error, so client sites can render an empty state.

Every uploaded file lives in the assets collection, stored in Vercel Blob through the backoffice and served at GET /api/v1/assets/{pathname}. Client sites typically proxy that under their own /api/blob/ route using the pathname. A service or a product embeds the pathname of its single image; a case study references whole asset documents, so its files arrive with their kind, MIME type, name, size and pixel dimensions resolved.