Delete additional identifier

DELETE /api/members/identifier/{identifierId}

Overview

Removes an additional identifier — an access card, wristband, fob or token that is not the member's primary card — by its value alone. Reach for it when you know the identifier that has been lost, replaced or issued in error but do not have, or do not want to supply, the member it belongs to.

The identifier is looked up by value across the whole tenant and permanently deleted; there is no soft-delete flag, no archive and no anonymised remnant. Only additional identifiers are searched. A value that is currently a member's primary card is not matched and comes back 404, so use DELETE {base_url}/api/members/{memberId}/identifier/{identifierId} when you need to clear a primary card.

Because the route carries no member id, this endpoint performs none of the member-scoped authorisation checks the rest of the identifier endpoints apply: any caller authorised for this API can delete any additional identifier in the tenant, including one belonging to a member other than the one their token identifies. Treat it as an administrative operation.

It is not idempotent in its status codes. The first successful call returns 204; repeating it returns 404, because the identifier has gone.

Endpoint

DELETE {base_url}/api/members/identifier/{identifierId}

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

Path parameters

NameTypeRequiredDescription
identifierIdstringYesThe identifier value to remove — the same string you sent as id when creating it with POST {base_url}/api/members/{memberId}/identifier, or that GET {base_url}/api/members/{memberId}/identifier returned. It is the value carried by the card or token, not a record id and not a member id. Only additional identifiers are searched, so a value held as a member's primary card will not be found.

Sample request

cURL
curl -X DELETE '{base_url}/api/members/identifier/{identifierId}' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true'

Errors

StatusMeaningWhen
404Not foundNo additional identifier holds that value — because it never existed, because a previous call already deleted it, or because the value is a member's primary card rather than an additional identifier. The response body is empty and does not say which of these applies.
500Internal server errorAn unexpected server-side failure while deleting. The response has no body.

This page as markdown · All pages · llms.txt