Skip to main content
The statistics/ endpoint lets you retrieve various statistics for your online shop from our shop system. Through the interface you can query statistics for form inquiries, transactions and payment methods, product ratings, orders and sales, and access statistics.

Supported methods

List of all supported methods.

Data persistence for statistics

The statistics data of the shop system is stored in three different aggregation levels:
  • Hourly data (per hour)
    This data provides the finest level of detail and enables precise analysis of short-term events, e.g. peaks in ordering behavior during a promotion.
    Storage duration: 3 weeks
    After that, the data is deleted automatically to limit the data volume.
  • Daily data (per day)
    This aggregation is suitable for medium- to long-term evaluations, for example to observe weekly trends or campaign progress.
    Storage duration: 3 months
  • Monthly data (per month)
    This data is geared towards long-term analyses, e.g. to evaluate seasonal fluctuations or annual sales development.
    Storage duration: 3 years
This staggered storage ensures that many details are available in the short term, while in the long term only aggregated information is retained.

Resources

Data table for inquiries

Example

Data table for orders

Example

Data table for sales

For GET statistics/sales

Example

For POST statistics/sales/product

Example

Example

Statistics for transactions and payment methods

Example

Methods for inquiries

GET statistics/inquiries

This method returns statistical evaluations for the inquiry functions used in the shop (e.g. contact form, call-back service, complaint, etc.). The data is returned separately for each subshop and can be aggregated by hour, day or month. The time range is defined via the from and to parameters in ISO 8601 format. To retrieve the data, the corresponding permissions to read statistics must be available.

Example

The example shown evaluates the number of inquiries in the period from 2024-02-29 to 2025-02-28 month by month — for the deutsch and english subshops.

Response

Filter fields

subshopID

Error codes

GET statistics/inquiries/duration

The processing times of the inquiries are returned. value indicates how many days were needed for processing. count indicates how often the value occurs. The time range is defined via the from and to parameters in ISO 8601 format. To retrieve the data, the corresponding permissions to read statistics must be available.

Example

Response

Filter fields

subshopID

Error codes

Methods for order statistics

POST statistics/orders/hours

This endpoint returns hourly aggregated order statistics for the specified period. In the request body, subshops can optionally be specified in order to restrict the evaluation. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Request body

Response

Error codes

POST statistics/orders/days

This endpoint returns daily aggregated order statistics for the specified period. In the request body, subshops can optionally be specified in order to restrict the evaluation. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Request body

Response

Error codes

POST statistics/orders/months

This endpoint returns monthly aggregated order statistics for the specified period. In the request body, subshops can optionally be specified in order to restrict the evaluation. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Request body

Response

Error codes

Methods for sales

GET statistics/sales

This endpoint returns revenues in the specified period, grouped by subshop and a selectable aggregation interval. The aggregation can be in hours, days or months. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

The example shown aggregates revenue in the period from 2025-04-22 to 2025-04-28 day by day.

Response

Error codes

GET statistics/soldProducts

This endpoint returns sales figures in the specified period, grouped by subshop and a selectable aggregation interval. The aggregation can be in hours, days or months. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

The example shown aggregates sales figures in the period from 2025-07-02 to 2025-09-30 month by month.

Response

Error codes

POST statistics/sales/product

This endpoint returns the sales figures of selected products in the specified period, grouped by date and subshop. The query is performed by providing a list of product IDs in the request body. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Request body

Response

Error codes

Methods for newsletter statistics

GET statistics/newsletter/subscribed

This endpoint returns the number of new newsletter subscribers in the specified period, grouped by the provided aggregation interval. The evaluation can be restricted to individual subshops via the subshopId filter. Without the filter_eq[subshopId] parameter, all subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopId

Error codes

GET statistics/newsletter/unsubscribed

This endpoint returns the number of newsletter unsubscribes in the specified period, grouped by the provided aggregation interval. The evaluation can be restricted to specific subshops via the subshopId filter. Without the filter_eq[subshopId] parameter, all subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopId

Error codes

Methods for product rating statistics

POST statistics/productrating

This endpoint returns all captured product ratings in the specified period, including rating texts, points, approval status and other metadata. In addition to the rating, the results also contain information such as subshop, product ID, the rater and any merchant comments. If the type field contains the values 1 (MostRated) or 2 (BestRated), average values and the number of ratings may also occur. It is possible to consider only specific subshops and, with type=0, only specific products. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Request body

Response

Error codes

POST statistics/productrating/average

This endpoint returns the average rating value of all captured product ratings in the specified period. The evaluation covers all ratings across all subshops. If the "subshops" field is provided, only the listed subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Request body

Response

Error codes

POST statistics/productrating/count

This endpoint returns the total number of all captured product ratings in the specified period. The count covers all ratings regardless of their approval status. If the "subshops" field is provided, only the listed subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Request body

Response

Error codes

POST statistics/productrating/averagecount

This endpoint returns the average rating value per product in the specified period. The evaluation covers all ratings across all subshops. If the "subshops" field is provided, only the listed subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Request body

Response

Error codes

Methods for transactions & payment methods

GET statistics/transactions

This endpoint returns a list of transactions with detailed order and payment information for the specified period, grouped by the selected aggregation interval. The evaluation can be restricted to individual subshops via the subshopId filter. If no subshop ID is provided at all, no data is returned. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/transactions/tableData

This endpoint returns a tabular overview of the revenues, grouped by payment method and country, for the specified period. The data is sorted by country and can additionally be limited via the subshopId and country filters. If no subshop ID or country is provided, no data is returned. The time range is defined via the from and to parameters in ISO 8601 format. To use it, permissions to read statistics are required.

Example

Response

Filter fields

subshopID, country

Error codes

GET statistics/transactions/countries

This endpoint returns a list of all countries from which orders were placed in the shop. The returned country values can be used for filtering in other transaction endpoints. To use it, permissions to read statistics are required.

Example

Response

Error codes

GET statistics/transactions/methods

This endpoint returns a list of all payment methods used in the shop that have been captured in the transaction data. The listed payment methods can be used for filtering in further statistical evaluations. To use it, permissions to read statistics are required.

Example

Response

Error codes

Methods for access statistics

GET statistics/access/currentVisitors

This endpoint returns the current number of visitors as well as the comparison value at the same time on the previous day. The evaluation can be restricted to specific subshops via the subshopId filter or performed across subshops. Without the filter_eq[subshopId] parameter, all are taken into account. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/visitors

This endpoint returns the number of visitors (human users only) in the specified period, grouped by an aggregation interval. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/robots

This endpoint returns the number of accesses by search engine bots in the specified period. The data lets you evaluate bot traffic to the shop. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Error codes

GET statistics/access/all

This endpoint returns the total number of visitors in the specified period. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/httpCodes

This endpoint returns an overview of how often certain HTTP status codes occurred in the specified period, including the associated paths. The data lets you analyze system responses (e.g. 200, 301, 500) to different access requests. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Error codes

GET statistics/access/os

This endpoint returns an overview of how often certain operating systems were used for accesses to the shop in the specified period. The evaluation can be selectively restricted to individual subshops and device types via the subshopId and device filters. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response:

Filter fields

subshopID, device

Error codes

GET statistics/access/browser

This endpoint returns an evaluation of how often certain browsers — grouped by versions — were used in the specified period. The analysis can be restricted to specific subshops and device types via the subshopId and device filters. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID, device

Error codes

GET statistics/access/action

This endpoint returns an overview of how often certain shop actions were performed in the specified period. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/importantActionsRate

This endpoint returns information about how many sessions in which important actions were performed. These include:
  • Order
  • Voucher redemption
  • Registration
  • Address update
  • Submission of an inquiry
  • Adding a product to the cart
If the aggregation parameter is set (hour, day or month; without “s”), the output is grouped by time. In addition, a restriction to specific subshops can be applied via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To determine the rate for aggregated data, the sum of totalSessionCount.value for each subshop should first be calculated. Then the totalSessionCount.value values should be divided by the sum. To use it, read permissions for statistics are required.

Example

Response (aggregated data)

Response (non-aggregated data)

Filter fields

subshopID

Error codes

GET statistics/access/products

This endpoint returns a list of the most-visited products in the specified period, including access counts and product names. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/categories

This endpoint returns a list of the most-visited categories in the specified period, including access counts and category names. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/devices

This endpoint returns an overview of how often certain device types were used for accesses to the shop in the specified period. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/devicesList

This endpoint returns a list of all captured devices with which the shop was accessed, including the respective access counts. The data lets you analyze which end devices were used for shop visits. Unlike GET statistics/access/devices, the time range does not need to be specified. To use it, read permissions for statistics are required.

Example

Response

Error codes

GET statistics/access/clicksCountPerSession

This endpoint returns the average number of clicks per visit (session) in the specified period, calculated exactly without rounding. The evaluation can be restricted to individual subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/clicksCountPerUser

This endpoint returns the average number of clicks per visitor in the specified period. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/trafficPeaks

This endpoint returns the times with the highest simultaneous user counts (traffic peaks) within a defined period, separated by subshop. Aggregation is done by hours, days or months and is required. In addition, a targeted restriction to individual subshops can be applied via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/sessionsWithoutRouting

This endpoint returns the number of sessions without further navigation in the shop (bounces) for a specific period, optionally grouped by time and subshop. If the aggregation parameter is set (hour, day or month; without “s”), the output is grouped by time. In addition, a restriction to specific subshops can be applied via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To calculate the bounce rate for aggregated data, first fetch the number of sessions for each subshop with GET statistics/access/totalSessionCount and divide filteredSessionsCount.value by this number. For non-aggregated data — simply divide the response by the number of sessions in the same period. To use it, read permissions for statistics are required.

Example

Response (aggregated data)

Response (non-aggregated data)

Filter fields

subshopID

Error codes

GET statistics/access/totalSessionCount

This endpoint returns the total number of all sessions in the specified period, optionally grouped by an aggregation interval. If the aggregation parameter is set (hour, day or month; without “s”), the output is grouped by time. In addition, a restriction to specific subshops can be applied via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response (aggregated data)

Response (non-aggregated data)

Filter fields

subshopID

Error codes

GET statistics/access/referer

This endpoint returns a list of the referrer domains through which visitors reached the shop in the specified period. The evaluation can be restricted to individual subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/countries

This endpoint returns an overview of the number of page views by country of origin in the specified period. The evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/lengthOfStay

This endpoint returns the average length of stay in seconds for a defined period, optionally grouped by a supplied aggregation interval. The aggregation parameter should always be present. The aggregation is done using the values hours, days or months; with other values, no aggregation occurs. In addition, the evaluation can be restricted to specific subshops via the subshopId filter. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response (aggregated data)

Response (non-aggregated data)

Filter fields

subshopID

Error codes

GET statistics/access/allPageViews

This endpoint returns the total number of all page views in the specified period, optionally grouped by time interval and subshop. If the aggregation parameter is provided (hour, day or month; without “s”), the data is returned grouped accordingly. Via the subshopId filter the evaluation can be restricted to individual subshops. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response (aggregated data)

Response (non-aggregated data)

Filter fields

subshopID

Error codes

GET statistics/access/accountType

This endpoint returns an evaluation of the customer types that accessed the shop in the specified period. The analysis is optionally filtered by one or more subshops. Without a filter, all subshops are taken into account. The time range is defined via the from and to parameters in ISO 8601 format. Possible values for accountType: -1 → Not selected
0 → Guest
1 → New customer
2 → Customer
To use it, read permissions for statistics are required.

Example

Response

Filter fields

subshopID

Error codes

GET statistics/access/browserList

This endpoint returns a list of all browsers used to access the shop, including the respective access counts. The data is used to analyze the browsers in use among shop visitors. Unlike GET statistics/access/browser, the time range does not need to be specified. To use it, read permissions for statistics are required.

Example

Response

Error codes

GET statistics/access/OSList

This endpoint returns an overview of all operating systems through which accesses to the shop occurred, including the respective access counts. The data lets you evaluate the platforms used by shop visitors. Unlike GET statistics/access/os, the time range does not need to be specified. To use it, read permissions for statistics are required.

Example

Response

Error codes

GET statistics/access/actionsList

This endpoint returns a list of all actions captured in the shop and their respective frequencies. The data tells you how often certain user actions such as page views or checkout steps were performed. Unlike GET statistics/access/action, the time range does not need to be specified. To use it, read permissions for statistics are required.

Example

Response

Error codes

Additional endpoints

GET statistics/newlyRegistered

This endpoint returns the number of new registrations in the specified period, grouped by a selectable aggregation interval. The time range is defined via the from and to parameters in ISO 8601 format. The aggregation is done in hours, days or months; other values are converted automatically accordingly. To use it, read permissions for statistics are required.

Example

Response

Error codes

POST statistics/visitors

This endpoint returns the daily visitor numbers of the subshops for a freely selectable period. The time range is defined via the from and to parameters in ISO 8601 format. To use it, read permissions for statistics are required.

Example

Response

Error codes

Support

Bei technischen Fragen und Hilfestellungen ist unser Support-Team für Sie erreichbar: Zum Kundenportal Bitte senden Sie uns eine möglichst detaillierte Beschreibung sowie Screenshots, Requests/Antworten, damit wir Ihre Anfrage zeitnah und zielführend beantworten können.