HACCP records, where your software already is
BackResto is the compliance app food-service teams fill in every day. The Partner API hands you what they recorded (goods-in checks, temperatures, cooling, cleaning, labels, photographs) for the restaurants that explicitly granted you access, and nothing else.
curl https://api.backresto.com/v1/restaurants/$RESTAURANT_ID/collections/temperature-records/records \
-H "Authorization: Bearer $BACKRESTO_PARTNER_API_KEY" \
--get \
--data-urlencode "limit=100"What you can build
Read-only throughout, with one authentication scheme and one error shape: twenty-six record types, deliveries included, through one generic envelope.
Temperature records
Fridge and freezer readings, taken by staff or reported by a sensor, with the thresholds that say whether each one was in range.
Traceability labels
Every secondary shelf-life label a restaurant printed, with the printed file attached and a group id per print run.
Cleaning
The cleaning plan, the tasks actually ticked off, and the photographs proving it.
Collections & records
Twenty-six record types (deliveries, temperatures, cooling, cleaning, fryer checks, labels, drive files) in one envelope, each behind its own grant.
MCP for AI clients
A read-only MCP server that puts the same five operations in front of an AI client, without widening what the key may reach.
Scoped access keys
One key, scoped to named restaurants and named scopes, issued once the restaurants have agreed to it. Ask by email; it arrives the same day.
Access the restaurant agreed to
There is no sign-up. A key is issued by hand, scoped to named restaurants and named scopes, and only once the restaurants in question have agreed to it. It reaches those restaurants and nothing else, and no request you can make widens that.
So “how do I get access?” is a form: your company, the restaurants you need, the scopes you want. We confirm with them and send the key to the contact you name.
What to put in the request