A receipt as plain text
const url = 'https://api.aerandil.com/v1/fnb/receipts/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/text';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.aerandil.com/v1/fnb/receipts/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/text \ --header 'Authorization: Bearer <token>'The receipt as 42 columns of plain text (Font A on 80 mm paper) — the till’s preview, line for line what the printer prints: the supplier’s name, address and VAT number, the check, the time of supply, the lines, the total, VAT per rate (rate, net, VAT, VAT-inclusive total — VAT Notice 700 §16.6.1), the tenders and the receipt’s number on the property’s document chain. A pure function of the receipt’s snapshot. Read through hospitality.function.fnb_receipt under the caller’s own context: its grant, the house gate, and — for a till — the till’s own outlet (another outlet’s receipt is 403 outlet_out_of_scope).
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The hospitality.check_receipt a settled check was issued.
Responses
Section titled “Responses”The receipt, 42 columns, one line feed per line.
Headers
Section titled “Headers”Always no-store. Object and link state is live data and is never cacheable.
The bearer authenticated but does not hold the scope this operation requires.
Structured error wrapper. Every non-2xx response from any Aerandil endpoint serialises to this shape; the HTTP status carries the failure class (4xx/5xx), the body adds a stable code for programmatic dispatch plus a human-readable message.
object
object
Stable, programmatic error code (e.g. unauthorized, forbidden, not_found, invalid_body, invalid_url, precondition_failed, no_secondary_key). Clients dispatch on code, not on the message (which may be localised or contextualised in future versions).
Request-id correlation handle echoed on the request-id response header — support teams correlate without scraping logs.
Human-readable explanation of the failure.
Per-error structured detail. The shape varies by code (e.g. forbidden_action carries {"action": "..."}; precondition_failed carries {"current_version": N}).
Examplegenerated
{ "error": { "code": "example", "instance_id": "example", "message": "example", "parameters": "example" }}No such object in the caller’s tenant — which is also the answer when it exists in another tenant, by design.
Structured error wrapper. Every non-2xx response from any Aerandil endpoint serialises to this shape; the HTTP status carries the failure class (4xx/5xx), the body adds a stable code for programmatic dispatch plus a human-readable message.
object
object
Stable, programmatic error code (e.g. unauthorized, forbidden, not_found, invalid_body, invalid_url, precondition_failed, no_secondary_key). Clients dispatch on code, not on the message (which may be localised or contextualised in future versions).
Request-id correlation handle echoed on the request-id response header — support teams correlate without scraping logs.
Human-readable explanation of the failure.
Per-error structured detail. The shape varies by code (e.g. forbidden_action carries {"action": "..."}; precondition_failed carries {"current_version": N}).
Examplegenerated
{ "error": { "code": "example", "instance_id": "example", "message": "example", "parameters": "example" }}