WellnessLiving API (UAT) - v1.2026-02
  1. report
WellnessLiving API (UAT) - v1.2026-02
  • WellnessLiving API - [Feb-2026]
  • Auth
    • Authentication
  • appointment
    • /v1/appointment/book/asset/category
    • /v1/appointment/book/asset/list
    • /v1/appointment/book/asset/service
    • /v1/appointment/book/finish
    • /v1/appointment/book/finish
    • /v1/appointment/book/payment/paymentPost
    • /v1/appointment/book/product
    • /v1/appointment/book/schedule/calendar
    • /v1/appointment/book/schedule/day-time
    • /v1/appointment/book/service/category
    • /v1/appointment/book/service/list
    • /v1/appointment/book/staff/list
  • book-process
    • /v1/book/process/info
    • /v1/book/process/payment
    • /v1/book/process/purchase
    • /v1/book/process/purchase/element/list
  • business-data
    • /v1/business
    • /v1/business/franchise/location
    • /v1/business/skin
  • catalog
    • /v1/catalog/list
    • /v1/catalog/staff/catalog/list
  • classes
    • /v1/classes/list
    • /v1/classes/promotion
    • /v1/classes/view/element
  • collector-debt
    • /v1/collector/debt/list
    • /v1/collector/debt/pay
    • /v1/collector/debt/transaction
  • drive
    • /v1/drive/product/image/upload
  • ecommerce
    • /v1/ecommerce/order/sync
  • event
    • /v1/event/book/list
    • /v1/event/book/view/element
    • /v1/event/list
  • lead
    • /v1/lead/info
    • /v1/lead/info
  • location
    • /v1/location/list
    • /v1/location/view
  • login
    • /v1/login/attendance/list
    • /v1/login/search/settings
    • /v1/login/search/settings
    • /v1/login/search/staff-app/list
  • member
    • /v1/member/info
  • profile
    • /v1/profile/contract
    • /v1/profile/create
    • /v1/profile/fields
    • /v1/profile/purchase/list
    • /v1/profile/purchase/list/element
  • promotion
    • /v1/promotion
    • /v1/promotion/list
  • purchase
    • /v1/purchase/receipt
  • report
    • /v1/report/data
      GET
    • /v1/report/query
      POST
  • report-dev
    • /v1/report/customization-form
    • /v1/report/filter-info
  • schedule
    • /v1/schedule/class/list
    • /v1/schedule/class/view
    • /v1/schedule/class/view
    • /v1/schedule/page/element
    • /v1/schedule/page/list
    • /v1/schedule/tab
  • shop
    • /v1/shop/category
  • staff
    • /v1/staff/list
    • /v1/staff/view
  • user
    • /v1/user
  • visit
    • /v1/visit/status
  1. report

/v1/report/data

GET
/v1/report/data

Overview#

Retrieves tabular report data for a specific business and region. This endpoint is typically used to power reporting views (e.g., client or membership lists) where each row represents an entity and columns are returned dynamically based on the selected report.

Authorization#

Uses bearer-style auth via the TOKEN variable.
Ensure TOKEN is set (for example, in the active environment) before sending the request. It should contain a valid access token for the target UAT environment.

Query Parameters#

id_region (number, required)
Region identifier used to scope the report data (e.g., data center or deployment region).
k_business (number, required)
Unique business identifier. Only report data for this business is returned.
id_report (number, required)
Identifier of the report definition to execute (e.g., “Client List”, “Login List”, or other configured reports).

Response (200 OK)#

A successful response returns a JSON object with the main keys below:
status (string)
Overall result of the call. For successful calls this is typically "ok".
a_data (object)
a_row (array)
Collection of result rows for the requested report.
Each element contains:
a_data_api (object): Field values for the row (for example s_firstname, s_lastname, s_mail, s_name, a_member_group, url_photo, and other report-specific fields).
dt_since_local (object): Local date/time metadata for the row (e.g., dt_date).
Additional row-level fields such as s_note, uid, member, etc., depending on the report configuration.
a_total (object)
Aggregated metrics for the report, keyed by internal identifiers (e.g., i_login_type.\*).
Each entry typically includes:
is_prospect (boolean): Indicates whether the segment represents prospects.
s_title (string): Human-readable label (e.g., "Active Member", "Prospect").
s_value (number): Aggregate count or value for that segment.
Additional metadata fields such as k_log, s_version, and __a_message may also be present and are primarily used for internal logging, versioning, or additional localized messages related to the report.

Request

Query Params

Responses

🟢200
application/json
Body

Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request GET '/v1/report/data?id_region={{id_region}}&k_business={{k_business}}&id_report=33' \
--header 'Content-Type: text/plain' \
--data-raw ''
Response Response Example
{}
Modified at 2026-02-26 17:13:05
Previous
/v1/purchase/receipt
Next
/v1/report/query
Built with