Skip to main content
Your app doesn’t just have an API — it has a written contract for that API. The build authors an OpenAPI specification and leans on it throughout: it drives generated checks and keeps the code honest against what was promised. That contract belongs to you, so Creator hands it over.

​
The two downloads

Available from the publish dialog (the “Your app’s API” row) and the Tests tab:
  • The contract — your app’s OpenAPI specification (YAML). Feed it to any OpenAPI tooling: client generators, API gateways, documentation renderers, or another team’s linter.
  • A Bruno collection — a zip of API test requests, one per declared route, pointed at your app. Bruno is an open-source API client; the collection is plain files, so it also drops straight into a git repo next to your exported code.
Both downloads are authenticated — they’re your project’s artifacts, fetched with your session, not public links.

​
Why this matters for handoff

A client taking ownership of an app gets three things from Creator: the code, the contract (this page), and the receipts. The contract is the piece their next developer will actually open first — it answers “what does this thing’s API do” without reading the source.
If your app is UI-only and has no API, there’s no contract to download — the row simply doesn’t appear, rather than offering a file that doesn’t exist.