---
title: "Get one lead"
method: GET
path: "/leads/{id}"
tags: ["Leads"]
---

# Get one lead

`GET /leads/{id}`

Returns details of a specific lead. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals.

## Path parameters

- `id` string, uuid, required

## Response `200`

Successful response containing payload in the `data` field

- object
  - `success` boolean
  - `data` object
    - `id` string, uuid — The unique ID of the lead in the UUID format
    - `title` string — The title of the lead
    - `owner_id` integer — The ID of the user who owns the lead
    - `creator_id` integer — The ID of the user who created the lead
    - `label_ids` string[] — The IDs of the lead labels which are associated with the lead
    - `person_id` integer, nullable — The ID of a person which this lead is linked to
    - `organization_id` integer, nullable — The ID of an organization which this lead is linked to
    - `source_name` string — Defines where the lead comes from. Will be `API` if the lead was created through the Public API and will be `Manually created` if the lead was created manually through the UI.
    - `origin` string — The way this Lead was created. `origin` field is set by Pipedrive when Lead is created and cannot be changed.
    - `origin_id` string, nullable — The optional ID to further distinguish the origin of the lead - e.g. Which API integration created this Lead.
    - `channel` integer, nullable — The ID of your Marketing channel this Lead was created from. Recognized Marketing channels can be configured in your <a href="https://app.pipedrive.com/settings/fields" target="_blank" rel="noopener noreferrer">Company settings</a>.
    - `channel_id` string, nullable — The optional ID to further distinguish the Marketing channel.
    - `source_deal_id` integer, nullable — The ID of the deal if the lead was converted from a deal.
    - `is_archived` boolean — A flag indicating whether the lead is archived or not
    - `was_seen` boolean — A flag indicating whether the lead was seen by someone in the Pipedrive UI
    - `value` object, nullable — The potential value of the lead represented by a JSON object: `{ "amount": 200, "currency": "EUR" }`. Both amount and currency are required.
      - `amount` number, required
      - `currency` string, required
    - `expected_close_date` string, date, nullable — The date of when the deal which will be created from the lead is expected to be closed. In ISO 8601 format: YYYY-MM-DD.
    - `next_activity_id` integer, nullable — The ID of the next activity associated with the lead
    - `add_time` string, date-time — The date and time of when the lead was created. In ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ.
    - `update_time` string, date-time — The date and time of when the lead was last updated. In ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ.
    - `visible_to` '1' | '3' | '5' | '7' — The visibility of the lead. If omitted, the visibility will be set to the default visibility setting of this item type for the authorized user.<table><tr><th>Value</th><th>Description</th></tr><tr><td>`1`</td><td>Owner &amp; followers (private)</td></tr><tr><td>`3`</td><td>Entire company (shared)</td></tr></table>
    - `cc_email` string — The BCC email of the lead

## Other responses

- `404` — A resource describing an error

---

[API](https://skmtc.net/pipedrive/apis/pipedrive-api-v1.md) · [All operations](https://skmtc.net/pipedrive/apis/pipedrive-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pipedrive/pipedrive-api-v1/versions/bf863a979545/schema)