---
title: "Get a lead by GLID (one-call lookup)"
method: GET
path: "/api/v1/leads/by-ref/{lead_ref}"
tags: ["leads", "leads"]
---

# Get a lead by GLID (one-call lookup)

`GET /api/v1/leads/by-ref/{lead_ref}`

## Request

- Base URL: `https://app.goodleads.club` (the document declares no server; this is the origin it was published from)
- URL: `https://app.goodleads.club/api/v1/leads/by-ref/{lead_ref}`
- Auth: API key in header `X-API-Key`

Full lead detail by GLID — the persistent human-readable reference
(e.g. `GL-CO-00042`).

Use this when you already know a lead's GLID (from a CRM, a Slack message,
a customer email, etc.) and want its full record in one call. Equivalent to
calling `POST /leads/browse` with `{"filters":[{"field":"lead_ref","op":"eq",...}]}`
then `GET /leads/{entity_id}` — but one HTTP hop instead of two.

GLIDs are case-insensitive; the canonical form is uppercase.
Returns the same shape as `GET /leads/{entity_id}`. Contact fields are
masked under the commerce free/paid boundary; the response's
`access_level` field signals "full" vs "preview".

## Path parameters

- `lead_ref` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/goodleads/apis/formation-gtm-api.md) · [All operations](https://skmtc.dev/goodleads/apis/formation-gtm-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goodleads/apis/formation-gtm-api/revisions/2068d13a82cf?raw)