Record a visit
Each line is a food from your list and how many; its pounds are the count times what one weighs, fixed on the day. A retired food is refused. Whether person_id is allowed, required or refused follows your pantry’s records setting, and the refusal says which. While the pantry is switched off, every path here but the settings answers 404 saying so. Needs write on People.
Authorizations
An API key from Settings, API keys. It starts with rc_live_.
Body
1 - 40 elementsA household (a person with the pantry_client role). Refused when your pantry keeps no names; required when it keeps every name. Required when it keeps every name, unless the visit is to a partner agency.
Today when left out. Not a day still to come.
One of your locations, by its ID in Settings.
Left out, the household's own dogs on file on that day; 0 for a walk-up.
0 <= x <= 5000 <= x <= 5000 <= x <= 500One of your partner agencies, by its organization ID. Not with person_id. Allowed whatever your records setting is.
Response
The visit.
The household, or null for a walk-up.
Every line's pounds, added up.
The site, as one of your locations in Settings.
A partner agency the food went to, instead of a household.
On a visit just recorded: what it did against your rules, in words. Empty when it broke none.
