Skip to main content
Retrieve and display digital receipts for customer purchases in your own channels — a customer portal, a mobile app, or email. Receipts are rendered from the purchase data you load into Lobyco: on request the Receipts API fetches the stored purchase, enriches it (loyalty points, discounts, store details) and returns it as JSON, rendered HTML or a barcode.

​
Before you start

  • Receipts are built from loaded purchases, so Transaction Data must already be flowing. Receipt content directly reflects what you send there — products, prices, taxes, discounts and payment methods.
  • These are server-to-server calls — see API Authentication.

​
How a receipt becomes available

  1. The POS completes a transaction.
  2. Your system sends the purchase to the Purchase Load API.
  3. The Purchase Load API processes and stores the purchase.
  4. A purchase-loaded event is triggered.
  5. The Receipts API indexes the receipt for quick lookup.
  6. The receipt becomes available through the retrieval endpoints.
The receipt index stores summary information (store ID, customer ID, total amount, purchase date) for fast lookups, while the detailed purchase data remains in the Purchase Load API.

​
Retrieve receipts

1

​
List the customer’s receipts

GET /v1/receiptsQuery the receipt list for a customer. Lists are paginated — page through until you have the range you need, and keep the receiptId of any receipt you want to render.
2

​
Fetch a single receipt

GET /v1/receipts/{receiptId}Retrieve the full receipt for display — as structured JSON for your own rendering, or as HTML for email delivery or a web view.
3

​
[Optional] Get the barcode

GET /v1/receipts/{receiptId}/barcodeRetrieve a barcode representation of the receipt identifier for scanning and verification, for example at a returns desk.

​
Failure and edge cases

Receipts only exist after the purchase has been loaded. If you request a receipt before its purchase data has reached the Purchase Load API, the API returns 404. Expect a short delay between transaction completion and receipt availability — treat an early 404 as “not yet”, not “never”, and retry after a short interval.
Last modified on August 13, 2026