Set a user's client ID

Attaches a client ID to an existing Bardge user that does not have one yet — for example a user who signed up directly by email, or one you are migrating over from your previous system.

A client ID here is the enrollee's member ID: the identifier for the individual in your system. It is not your company or reseller ID.

Identify the user with user_id (preferred) or email. An email must resolve to exactly one user in your account; if it matches none or several, the request is rejected rather than guessed at.

Setting a client ID is permanent. If the user already has one, the request is rejected and nothing changes — repeating the call with the same value is a safe no-op. Attaching a client ID never affects the user's existing bookings, passes or credits, and does not change access codes that have already been issued.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location '/v3/api/business/reseller/clients/set_client_id' \ --header 'Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "user_id": "usr_10482", "email": "ada@example.com", "client_id": "client_abc123" }'

{ "object": "client", "id": "client_abc123", "user_id": "usr_10482", "first_name": "Ada", "last_name": "Okafor", "email": "ada@example.com", "phone": "08012345678", "status": "active", "created": 1746700000, "message": "Client ID set successfully" }

Request

Responses