Retrieve a member's basic profile details

GET /api/members/{memberId}/profile

Success: 200 OK

• Products: Operator (FOH), Consumer (CONSUMER), Integrations (INTEGRATIONS) (any one of these products, not all)
• Features: Online Bookings (ONLINEBOOK), Online Joining (ONLINEJOIN), TRP Integration (TRP), DataHub (4Global) Integration (DATAHUB), Front of House Generic Access (FOHGENERIC) (any one of these features, not all)

Overview

Returns one member's profile, addressed by member ID: who they are, which centre they belong to, and — when you ask for them — their addresses, contact details, current status and subscriptions. It is the single-member counterpart of List all member profiles with filtering and pagination, which returns the same profile shape in bulk.

This endpoint has two response shapes, and which one you get is decided by the features on your access token, not by anything in your request. A caller whose token carries the DataHub feature and none of the privileged full-profile features (TRP, online booking or online join) is deliberately given a reduced profile — member ID, home site, gender, join date, date of birth, postcode and subscriptions, and nothing else. That reduced shape is what the fields below describe. Every other caller receives the full profile, which adds the member's name and title, both addresses, contact details, price level, site, status, last recorded visit, and counts of attendance and activity over the past 30 days. The redaction happens on the way out, so the omitted fields are simply absent rather than null — build against the shape your own credentials actually produce, and re-check it if the features on your integration change.

The four include* parameters control how much of the profile is loaded. All default to false, so a bare call returns the member's core details and leaves addresses, contact details, status and subscriptions out. They apply to the reduced shape too: subscriptionDetails is only populated there if you set includeSubscriptions=true.

Two details worth knowing before you map the response. Members with no title recorded come back as UNKNO / Unknown rather than null: the endpoint substitutes a default. And for a junior member who inherits their email address from the primary member on their linked account, this endpoint resolves the address from that primary member before returning it, preferring whichever of the primary member's home and work addresses is flagged as primary and falling back to the other if it is blank — the bulk list endpoint does not do this.

Access is checked against your token: the member ID in the path must be the member the token was issued for, or a member linked to them, such as a parent reading a child's profile.

Endpoint

GET {base_url}/api/members/{memberId}/profile

{base_url} is the environment URL issued to your integration. See Authenticating with Gladstone APIs.

Path parameters

Query parameters

Sample request

curl -X GET '{base_url}/api/members/{memberId}/profile' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true'

Response fields

Sample response

{
  "memberId": 12345,
  "homeSiteId": "string",
  "gender": {
    "id": 12345,
    "name": "string",
    "translations": [
      {
        "type": "string",
        "culture": "string",
        "text": "string"
      }
    ]
  },
  "joinDate": "2026-08-14T19:00:00Z",
  "dateOfBirth": "2026-08-14T19:00:00Z",
  "postcode": "string",
  "subscriptionDetails": [
    {
      "id": "string",
      "siteId": "string",
      "membershipRef": 1,
      "autoRenewInd": 1,
      "renewalStopDate": "2026-08-14T19:00:00Z",
      "expiryDate": "2026-08-14T19:00:00Z",
      "lastModifiedDate": "2026-08-14T19:00:00Z",
      "createdOn": "2026-08-14T19:00:00Z",
      "startDate": "2026-08-14T19:00:00Z",
      "membershipStatus": "string",
      "subscriptionGroups": [
        {
          "id": "string",
          "description": "string"
        }
      ]
    }
  ]
}

Errors

This page as markdown · All pages · llms.txt