Get member picture

GET /api/members/{memberId}/base64-member-picture

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), Front of House Generic Access (FOHGENERIC) (any one of these features, not all)

Overview

Retrieves a member's profile photograph — the one staff see at reception to confirm who is presenting a card — together with the member's photo upload history and the upload limits that apply to them. Use it to show the current photo, and to tell the member whether they can change it now and, if not, when they can.

A member with no photograph returns 200 with picture set to null, not 404; the upload history and limits are still returned. Most members typically have no picture, so treat a null picture as an ordinary outcome. A 404 now means the member itself does not exist.

Two limits govern a new photo, and both are reported in the response:

• Change frequency. After a successful upload the member must wait uploadFrequency days before uploading again. They can upload now if lastSuccessfulPhotoUploadUtc is null, or if that time plus uploadFrequency days is in the past; otherwise that same sum is the earliest time they can. A call to Update member picture made sooner is refused with 409.
• Photo-check attempts. Before a photo is stored it can be put through Gladstone's photo checks (face detection and the other content checks). Each completed check — accepted or rejected — counts as one attempt, and a member may make at most maxRetries attempts in a 24-hour window. Checks that fail for a server-side reason are not counted. A successful upload resets the count to 0.

The attempt count is not cleared when its window ends; it is reset the next time the member makes an attempt. Work out whether it is still current yourself: if pictureValidationAttemptWindowStartUtc is null or more than 24 hours ago, treat the count as 0. If it is within the last 24 hours and pictureValidationAttemptCount has reached maxRetries, no further attempt is accepted until 24 hours after the window start. A maxRetries of 0 means attempts are unlimited.

The image comes back raw: no data URI prefix, no content type and no dimensions. You are told nothing about the format, so if you need to render it you will have to sniff the bytes or assume what your operator uploads.

This endpoint is single-member only — a linked member's picture cannot be read with a primary member's token.

Endpoint

GET {base_url}/api/members/{memberId}/base64-member-picture

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

Path parameters

Sample request

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

Response fields

All date-times are UTC. Treat them as UTC whether or not the value carries a Z suffix.

Sample response

{
  "picture": "iVBORw0KGgoAAAANSUhEUgAA...",
  "lastSuccessfulPhotoUploadUtc": "2026-04-14T09:31:07",
  "pictureValidationAttemptCount": 2,
  "pictureValidationAttemptWindowStartUtc": "2026-10-12T08:02:44",
  "uploadFrequency": 180,
  "maxRetries": 5
}

{
  "picture": null,
  "lastSuccessfulPhotoUploadUtc": null,
  "pictureValidationAttemptCount": 0,
  "pictureValidationAttemptWindowStartUtc": null,
  "uploadFrequency": 180,
  "maxRetries": 5
}

Errors

This page as markdown · All pages · llms.txt