Skip to main content
Show a customer the total value of their benefits over a period of time. The Savings History endpoints are an aggregation layer: they consolidate Bonus Accounting with the Lobyco promotional services — Offers, Games and Challenges — so your app or website doesn’t have to query each service separately.

​
Before you start

  • Authentication must be working — see API Authentication.
  • The endpoints serve web and app channels (/web/v1/…) and return application/json.

​
Read the savings

1

​
Fetch the statements

GET /web/v1/statementsRetrieve the customer’s savings statements for the period. The list is paginated — see below.
2

​
Fetch the statistics

GET /web/v1/statisticsRetrieve the aggregated totals to headline the savings view.

​
Pagination

List endpoints use cursor-based pagination:
  1. Include the limit parameter to set the page size.
  2. Read the NextCursor field from the response.
  3. Pass that value as the cursor parameter on the next request.
  4. Stop when NextCursor is null or empty.

​
Localization

Use the Accept-Language header (for example en, dk) to control the language of the localized display names in the response. It defaults to en.

​
Failure and edge cases

Because this is an aggregation over several services, a benefit appears here once its source service has recorded it — a just-completed purchase may take a moment to show up in the savings view.
Last modified on August 13, 2026