# Documentation

> The BackResto Partner API, end to end. Start with the quickstart if you already hold a key.

Source: https://developers.backresto.com/en/docs

- [Introduction](https://developers.backresto.com/en/docs/introduction.md): What the BackResto Partner API exposes today, what it deliberately does not, and who decides.
- [Getting a key](https://developers.backresto.com/en/docs/access.md): How to ask for a Partner API key, what to put in the request, and what comes back.
- [Quickstart](https://developers.backresto.com/en/docs/quickstart.md): From a key to your first records and a delivery photograph in five minutes, with curl.
- [Authentication](https://developers.backresto.com/en/docs/authentication.md): Partner keys, the twenty-six scopes, what a grant means, and how to rotate without downtime.
- [Errors](https://developers.backresto.com/en/docs/errors.md): One machine-readable problem document for every failure, and what each type means for your retry logic.
- [Pagination](https://developers.backresto.com/en/docs/pagination.md): How to walk any collection with an opaque cursor, and how to keep a copy of it up to date.
- [Rate limits](https://developers.backresto.com/en/docs/rate-limits.md): The per-key budget, the one header that describes it, and how to stay under it.
- [Collections & records](https://developers.backresto.com/en/docs/collections.md): The twenty-six record collections, the snapshot envelope they share, and how to walk one.
- [Temperatures](https://developers.backresto.com/en/docs/temperatures.md): Fridge and cooking temperatures, taken by a person or reported by a sensor. Three collections, and what tells them apart.
- [Traceability labels](https://developers.backresto.com/en/docs/traceability-labels.md): The secondary labels staff print and stick on a container, with the printed file attached and a group id per print run.
- [Deliveries](https://developers.backresto.com/en/docs/deliveries.md): Goods-in checks and the photographs taken at reception: two collections, every field, and what they mean on the shop floor.
- [Cleaning](https://developers.backresto.com/en/docs/cleaning.md): The cleaning plan, the tasks actually done and the photographs proving it. Three collections, and what a missing record does not prove.
- [Fryers](https://developers.backresto.com/en/docs/fryers.md): The fryers and their oil quality checks. Two collections, and why the measured value can be missing while the decision never is.
- [Cooling & food processes](https://developers.backresto.com/en/docs/food-processes.md): Cooling, freezing, reheating and transport. Four collections recording a temperature transition, and what an unfinished one looks like.
- [Surface analyses](https://developers.backresto.com/en/docs/surface-analyses.md): Surface swabs. What was tested, whether it passed, and the action plan when it did not.
- [Documents](https://developers.backresto.com/en/docs/drive-files.md): The restaurant's own document store (certificates, procedures, reports), each record a filed file with its own media type.
- [Catalogue](https://developers.backresto.com/en/docs/catalogue.md): Suppliers, products and in-house preparations, the reference lists the rest of the record points at.
- [Facilities & people](https://developers.backresto.com/en/docs/facilities.md): The site, its staff, its zones and its machines. The fixed map every temperature reading hangs off.
- [MCP server](https://developers.backresto.com/en/docs/mcp.md): Connect Claude, Cursor, Codex or any MCP client to a restaurant's compliance records with one URL and your API key.
- [Support & data completeness](https://developers.backresto.com/en/docs/support.md): What the current data does and does not cover, how the API is versioned, and how to reach a human.

The whole documentation in one file: https://developers.backresto.com/llms-full.txt