Skip to main content
GET
/
api
/
leads
Get Lead
curl --request GET \
  --url https://app.puffle.ai/api/leads \
  --header 'Authorization: Bearer <token>'
{
  "leads": [
    {
      "id": "<string>",
      "type": "person",
      "name": {
        "full": "<string>",
        "short": "<string>",
        "aliases": [
          "<string>"
        ],
        "first": "<string>",
        "last": "<string>"
      },
      "lists": [
        {
          "id": "<string>",
          "name": "<string>"
        }
      ],
      "sources": [
        {
          "id": "<string>"
        }
      ],
      "createdAt": "<string>",
      "updatedAt": "<string>",
      "location": {
        "city": "<string>",
        "state": "<string>",
        "country": "<string>",
        "raw": "<string>"
      },
      "socials": [
        {
          "url": "<string>"
        }
      ],
      "contacts": [
        {
          "value": "<string>"
        }
      ],
      "attributes": {},
      "raw": {},
      "title": "<string>",
      "company": {
        "name": "<string>",
        "id": "<string>",
        "domain": "<string>"
      }
    }
  ],
  "nextCursor": "<string>"
}
CLI:
puffle lead
puffle lead --id <id> --type <type> --limit <limit> --cursor <cursor> --q <q> --name <name> --title <title> --role <role> --company <company> --domain <domain> --email <email> --industry <industry> --location <location>

Overview

Returns Leads for the effective user. Pass id to fetch one Lead. Otherwise, use type, limit, and cursor to page through workspace Leads by person or company. Use q for broad saved-Lead filtering across name, role/title, company, domain, industry, location, and work email fields. Use the narrower filters when you already know the field: name, title, role, company, domain, email, industry, or location. Use this endpoint when you need Leads across the whole workspace. Lists group these same Leads; they do not own separate copies of Lead data.

AI agent notes

Use this endpoint when you need Lead records independent of any single List. If you are rendering a List screen, prefer the List view or List Leads endpoints because they include membership and view-field context.The response is paginated. Keep the returned cursor and stop when no next cursor is present.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

id
string
type
enum<string>
Available options:
person,
company
limit
integer
Required range: 1 <= x <= 500
cursor
string
q
string

Broad text filter across saved Lead name, role/title, company, domain, industry, location, and work email fields.

Required string length: 1 - 200
name
string

Filter saved Leads by person or company name.

Required string length: 1 - 200
title
string

Filter saved person Leads by title.

Required string length: 1 - 200
role
string

Alias for title; filter saved person Leads by role.

Required string length: 1 - 200
company
string

Filter saved Leads by company name.

Required string length: 1 - 200
domain
string

Filter saved Leads by company or Lead domain.

Required string length: 1 - 200
email
string

Filter saved Leads by work email.

Required string length: 1 - 200
industry
string

Filter saved company Leads by industry.

Required string length: 1 - 200
location
string

Filter saved Leads by city, state, country, or raw location.

Required string length: 1 - 200

Response

Leads.

leads
object[]
required
nextCursor
string | null
required