Requests
What a customer's walk through a menu ends in: what they asked for, when, where and for whom. Read the inbox, answer what waits, check a customer's code at the counter, and change what is booked. Every move here is the one the dashboard and the staff phone menu make, under the same rules, and the customer is told by message where the business has linked Raven.
POSTCheck a code
Requires verifications:write. Before you serve someone, check the six-digit code they were given. A right code closes the request as verified, in one step. It matches only an approved request that is due now: from 12 hours before its time until the business's grace after it, or any time before fulfil_by for a request with no time. A wrong code is an answer, not an error: 200 with outcome wrong. Wrong codes are counted per key, and after the business's limit (5 unless it changed it) the key is locked out for its lockout (30 minutes unless changed).
What the check found. When it is verified, read the summary and the identity out before you serve.
One check: press Response on the sample to see one whole.
Amounts are integers in cents, with no currency. On failure the body is { error, code } instead.