---
title: "Query saved leads with the full filter set"
method: GET
path: "/api/v1/leads"
---

# Query saved leads with the full filter set

`GET /api/v1/leads`

## Request

- Base URL: `https://lyreleads.com`
- URL: `https://lyreleads.com/api/v1/leads`
- Auth: HTTP bearer

The richer sibling of /api/v1/results. Accepts the same 129 filter parameters the web app uses (enrolled among them), including relevance, email verification state, enrichment status, platform detections (cmsPlatform, crmPlatform, chatWidget, bookingSystem, emailMarketingPlatform), payments on the site (paymentProvider, excludePaymentProvider: a name such as Square, a group such as group:aggregator or group:high-risk, or __none__), what the site says (merchantSignal, excludeMerchantSignal: a statement or a group such as group:restricted), merchant-services views (merchantView, e.g. restricted-on-aggregator or chargeback-prone), data freshness, and change signals (signal + signalWindow). Every name, group and view is listed at GET /api/merchant-vocabulary. Multi-select filters are sent as a repeated query key. Use POST with a JSON body when the filter set is too large for a query string. Costs nothing: this reads leads you already own.

## Query parameters

- `page` integer
- `limit` integer
- `query` string
- `city` string
- `type` string
- `relevanceYes` boolean
- `hasVerifiedEmail` boolean
- `hasContactEmail` boolean
- `enrichmentStatus` string
- `enrolled` boolean
- `signal` string
- `signalWindow` string

## Response `200`

Paginated leads with total count

## Other responses

- `401`: Invalid API key

---

[API](https://skmtc.dev/lyreleads/apis/lyre-leads-api.md) · [All operations](https://skmtc.dev/lyreleads/apis/lyre-leads-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lyreleads/apis/lyre-leads-api/revisions/1c7c73cc355f?raw)