The Lookup section covers the third-party lookup flow for clients managed by another reseller. Use it to discover approved issuers, initiate a lookup for a client, and verify that lookup with the access code the client shares back.What you can do#
List approved issuers available for cross-party lookup
Initiate a third-party lookup against another reseller's client
Verify a pending lookup with the client's access code
Receive a lookup token that your business stores and reuses later when generating access codes
Get a client's credit balance and recent credit transaction history
Key concepts#
1.
Call GET /issuers to find the reseller that owns the client.
2.
Call POST /lookups with that issuer and the client ID.
3.
Collect the access code the client receives from the issuer.
4.
Call POST /lookups/{id}/verify with that access code.
5.
Store the returned lookup token on your own system and reuse it in Bardge-Lookup-Token when calling POST /access-codes.
There is no endpoint for retrieving lookup tokens later. The token is returned at verification time and must be persisted by your business for future use until it expires.Clients are identified by a client_id - a stable identifier assigned by the issuer reseller. Supply this ID when initiating a lookup against that issuer.An issuer is a reseller that has enabled third-party lookup on their account. When you need access to a client managed by a different reseller, supply that issuer's id when initiating the lookup. Use GET /issuers to retrieve the list of resellers currently approved for cross-party lookup.Lookup endpoints are designed for these common scenarios:| Scenario | Endpoint to use |
|---|
| Cross-party setup - discover which resellers support third-party lookup | GET /issuers |
| Start access delegation for a client managed by another reseller | POST /lookups |
| Confirm the client approved the lookup by sharing their access code | POST /lookups/{id}/verify |
| Generate future access codes for that looked-up client after verification | POST /access-codes with Bardge-Lookup-Token |
The lookup token returned by verification remains valid until the client's pass expires. Bardge does not provide a lookup-token listing or retrieval endpoint, so your business must store the token when it is issued.Access Codes - use the stored lookup token to generate client check-in codes later
Bookings - use the stored lookup token to book class appointments and spa services later
Passes - a valid active pass must exist for the issuer's client before lookup verification can succeed
Modified at 2026-05-19 13:57:57