# Get a lead

> Returns one captured lead by its sqid-encoded id.

Source: https://www.hey.support/docs/api/leads/get-lead

---

<ApiEndpoint method="GET" path="/leads/{id}" />

Responds 404 rather than 403 when the lead belongs to another workspace, so ids cannot be enumerated.

## Path parameters

<TypeTable
  type={{
  "id": { type: "string", description: "", required: true }
}}
/>

## Response `200`

<TypeTable
  type={{
  "id": { type: "string", description: "", required: true },
  "chatbot_id": { type: "string", description: "", required: true },
  "name": { type: "string", description: "", required: false },
  "email": { type: "string (email)", description: "", required: false },
  "phone": { type: "string", description: "", required: false },
  "status": { type: "string", description: "", required: true },
  "notes": { type: "string", description: "", required: false },
  "conversation_id": { type: "string", description: "", required: false },
  "created_at": { type: "string (date-time)", description: "", required: true }
}}
/>

### Errors

* `401` — Missing or invalid API key
* `404` — Not found
* `429` — Rate limit exceeded

Every error shares [one envelope](/docs/api/errors).

## Example

```bash
curl https://www.hey.support/api/v1/leads/<id> \
  -H 'Authorization: Bearer hs_live_…'
```
