---
title: "List recorded lead searches"
method: GET
path: "/find-leads/history/"
tags: ["find-leads"]
---

# List recorded lead searches

`GET /find-leads/history/`

## Request

- Base URL: `https://api.getoneprofile.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.getoneprofile.ai/find-leads/history/`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

The searches this workspace actually ran, recorded automatically: previews and imports alike, newest activity first. Re-browsing the same filters refreshes the latest entry rather than duplicating it.

## Response `200`

Successful Response

- LeadSearchHistoryListResponseSchema: The workspace's recorded searches, newest activity first.
  - `entries` LeadSearchHistoryEntrySchema[], required
    - `id` string, uuid, required
    - `query` object, required
    - `ran_at` string, date-time, required
    - `record_type` 'people' | 'companies' | 'signal_companies' | 'signal_people' | 'lookalikes' | 'local_businesses' | 'hiring_companies' | 'backlinks' | 'search_results' | 'post_authors', required: Which dataset a search runs against, and so which provider serves it. Values are persisted in String(16) columns, so every member must stay within 16 characters.
    - `rows_created` integer, nullable, required: Rows an import added; null when the search was only browsed.
    - `table_id` string, uuid, nullable, required: The table an import added rows to, when one did.
    - `total_matched` integer, required
    - `user_id` string, required

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `422`: Invalid request made to the API.
- `500`: Internal server error.
- `502`: Bad gateway error.
- `503`: Service unavailable.

---

[API](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile.md) · [All operations](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/llms.txt) · [OpenAPI document](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/revisions/4a6bd71e3f02?raw)