WellnessLiving API (UAT) - v1.2026-02
  1. member
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
      GET
  • 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
    • /v1/report/query
  • 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. member

/v1/member/info

GET
/v1/member/info

Overview#

Retrieves detailed profile information for a specific member within a given business and region. This endpoint is typically used by client applications to display or refresh a member’s account/profile data (e.g., name, contact info, membership status, and related attributes).

URL & Method#

Method: GET
URL: /v1/member/info
Full example: https://uat-api.wellnessliving.io/v1/member/info?id_region=2&k_business=49197&uid=2720946

Query Parameters#

All parameters are required unless otherwise noted:
id_region
Type: integer
Example: 2
Description: Internal region identifier that scopes the request to a specific geographic/tenant region. Ensure you use the correct region value for the environment (e.g., UAT vs. production).
k_business
Type: integer / string (ID)
Example: 49197
Description: Unique business identifier. This must match the WellnessLiving business (location/account) whose member data you want to retrieve.
uid
Type: integer / string (ID)
Example: 2720946
Description: Unique member (user) identifier within the specified business/region. The request returns information for this specific member only.

Authentication#

This endpoint requires an authenticated request.
Auth mechanism: Bearer token in the Authorization header.
Token source: Existing {{TOKEN}} variable configured in your environment/collection.
Expected header format:
Make sure the {{TOKEN}} value is valid for the target environment (UAT vs. production) and has permission to access member information for the specified k_business.

Typical Response & Usage#

Returns a JSON object containing the member’s core profile and related metadata (exact shape depends on your WellnessLiving configuration and API version).
Commonly used to:
Populate “My Account” or profile screens in client applications.
Pre-fill member details before booking, purchasing, or updating account data.
Validate that a given uid is active and associated with the specified k_business.

Notes & Expected Behavior#

If the uid does not exist or does not belong to the provided k_business/id_region, the API may return an error or an empty/partial payload depending on backend rules.
Ensure all three query parameters (id_region, k_business, uid) are present and consistent; mismatched values are a common cause of 4xx responses.
Use this request in conjunction with authentication/booking/purchase endpoints to keep member-facing workflows in sync with the latest profile data.

Request

Query Params

Responses

🟢200
application/json
Body

Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request GET '/v1/member/info?id_region={{id_region}}&k_business={{k_business}}&uid={{uid}}' \
--header 'Content-Type: text/plain' \
--data-raw ''
Response Response Example
{}
Modified at 2026-02-26 17:13:05
Previous
/v1/login/search/staff-app/list
Next
/v1/profile/contract
Built with