> ## Documentation Index > Fetch the complete documentation index at: https://docs.reply.io/llms.txt > Use this file to discover all available pages before exploring further. # Delete a Live Data search > **New.** This endpoint shipped recently. If anything about it is unclear or could work better for you, tell us in the [developer Slack](/slack). _Requires the `contacts:write` scope (or a broader one that includes it)._ Delete a Live Data search of your team, whatever its status. The search stops and its filters are free for a new search; the contacts it already added stay. The batch the search was working on when you delete it is not thrown away. Either it is still added, and charged, right after the delete, or it is kept for the next search you start with the same filters, which receives those people first. ## OpenAPI ````yaml /api-reference/bundled.yaml delete /v3/live-data/searches/{id} openapi: 3.1.0 info: version: 3.0.0 title: Reply API description: API for managing email sequences, contacts, and automation workflows servers: - url: https://api.reply.io security: - bearerAuth: [] tags: - name: Contacts description: Manage individual contacts - name: Contact Lists description: Manage contact lists and contact membership - name: Accounts description: Manage accounts (companies/organizations) - name: Account Lists description: Manage account lists and account membership - name: Custom Fields description: Manage custom contact fields - name: Prompt Actions description: Save reusable AI prompts and run them on contacts to fill custom fields - name: Contact Blacklist Rules description: Manage blacklist rules for domains, emails, and email exceptions - name: Live Data description: >- Find new contacts via Live Data searches and read typeahead values for the Live Data / Autopilot filter sidebar - name: Contact Enrichment description: >- Enrich contacts with emails, phone numbers, LinkedIn data, and AI-filled custom fields - name: Email Validations description: Estimate and schedule asynchronous email validation jobs - name: AI SDR Web Search description: Find contacts via AI-driven web search and review past searches - name: Sequences description: Manage email automation sequences - name: Sequence Steps description: Manage individual steps in sequences - name: Sequence Contacts description: Manage contacts within sequences - name: Sequence Folders description: Organize sequences into folders - name: Email Accounts description: Manage email accounts used for sending and receiving - name: Sequence Email Accounts description: Manage email accounts linked to sequences - name: LinkedIn Accounts description: Manage LinkedIn accounts for outreach - name: Sequence LinkedIn Accounts description: Manage LinkedIn accounts linked to sequences - name: Sequence Templates description: Manage sequence templates - name: Email Templates description: Manage email templates and template folders - name: Voices description: Manage cloned voices used for AI voice message steps - name: Schedules description: Manage email send schedules and timing - name: Holiday Calendars description: Manage holiday calendars for scheduling - name: Inbox description: >- Manage inbox threads — list/filter, read state, replies, category assignment, and meeting-intent flagging - name: Inbox Categories description: Manage per-team inbox thread categories and assign threads to them - name: Direct Outreach description: >- Send one-off outreach directly to a contact outside of any sequence — direct emails and LinkedIn connection requests, messages, InMails, and voice messages - name: Tasks description: Manage tasks and to-do items - name: Reports description: >- Generate and access performance reports across email, calls, tasks, LinkedIn, and team performance - name: AI SDR Sequences description: >- Manage AI SDR sequences and their AI SDR-specific settings — create, read settings, partial update, autopilot enable/disable/force-start, approval mode, sequence structure, and playbook/knowledge-base connections - name: AI SDR Sequence Structures description: >- Browse the sequence structures — reusable outlines of AI SDR sequence steps — that can be applied to AI SDR sequences - name: AI SDR Strategist description: Trigger AI Strategist runs - name: AI SDR Playbooks description: >- Manage AI SDR playbooks — tone, voice, and style guides applied during personalized message generation - name: AI SDR Knowledge Bases description: >- Manage AI SDR knowledge bases — collections of documents, links, reply handlers, and reengagement cards that inform the agent's responses - name: AI SDR Offers description: >- Manage AI SDR offers — bundles of company-context inputs (ICP, pain points, value propositions, etc.) used to personalize outreach - name: AI SDR Pending Approvals description: >- Review, send, regenerate, and provide feedback on AI-generated messages awaiting human approval - name: AI SDR Sequence Preview description: >- Read and regenerate per-contact previews of the messages a sequence will send, and provide feedback on preview messages - name: AI SDR Insights description: Read AI SDR insights for sequence contacts - name: AI SDR Intent Signals description: >- Read Reply industry IDs and technology slugs used in AI SDR intent-signal configuration (typeahead) - name: AI Prompts description: >- Manage the AI prompts used to configure sequence steps, and preview the output a prompt produces - name: AI SDR Learnings description: >- Manage the standing rules that shape how the AI writes — list, read, create, partially update and delete AI learnings - name: Registration description: Register the contact that domain purchases are filed under - name: Domains description: Find domains available to buy for outreach - name: Purchased Domains description: >- List the domains your team bought, with their subscription, setup and renewal state, and renew them - name: Pre-warmed Domains description: >- Find pre-warmed domains on sale, with mailboxes that are already warming, and list the ones your team bought - name: Mailboxes description: >- Add mailboxes to domains your team already bought, priced before you order, and reconnect them - name: User Account description: Account information and authentication verification - name: API Keys description: Create, list, edit and delete API keys, as the Settings page does - name: Teams description: Add existing users of your organization to its teams - name: Settings description: Manage team and user settings - name: Billing description: Subscription details and monthly active contacts usage - name: Rate Limits description: Your API rate limits, your current usage and the packages that raise them - name: Support Requests description: Raise and follow support requests with Reply's support team - name: Webhooks description: Manage webhook subscriptions and inspect delivery history - name: Background Jobs description: >- Track and cancel asynchronous background operations (e.g., email validation) - name: Attachments description: >- Upload file attachments used across email templates, sequence steps, and direct emails paths: /v3/live-data/searches/{id}: delete: tags: - Live Data summary: Delete a Live Data search description: >- **New.** This endpoint shipped recently. If anything about it is unclear or could work better for you, tell us in the [developer Slack](/slack). _Requires the `contacts:write` scope (or a broader one that includes it)._ Delete a Live Data search of your team, whatever its status. The search stops and its filters are free for a new search; the contacts it already added stay. The batch the search was working on when you delete it is not thrown away. Either it is still added, and charged, right after the delete, or it is kept for the next search you start with the same filters, which receives those people first. operationId: DeleteLiveDataSearch parameters: - name: id in: path required: true description: Search id schema: type: integer minimum: 1 responses: '204': description: Search deleted '401': description: >- Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme. content: application/problem+json: schema: allOf: - type: object title: Problem Details description: >- Bare RFC 9457 problem-details envelope. Returned by middleware-level errors that don't carry domain context: 401 Unauthorized (auth middleware), 429 Too Many Requests (rate-limit middleware), and route-level 404 / 405 / 415 (framework middleware). Business and validation responses extend this envelope and add additional fields — see `business-problem.model.yaml` (adds `code` slug) and `validation-problem.model.yaml` (adds `errors[]` array). properties: title: type: string description: Short, human-readable summary of the problem. status: type: integer description: HTTP status code. minimum: 100 maximum: 599 detail: type: string description: >- Human-readable explanation specific to this occurrence. - example: title: Unauthorized status: 401 detail: Authentication credentials are missing or invalid. '403': description: You do not have permission to manage searches content: application/problem+json: schema: allOf: - allOf: - type: object title: Problem Details description: >- Bare RFC 9457 problem-details envelope. Returned by middleware-level errors that don't carry domain context: 401 Unauthorized (auth middleware), 429 Too Many Requests (rate-limit middleware), and route-level 404 / 405 / 415 (framework middleware). Business and validation responses extend this envelope and add additional fields — see `business-problem.model.yaml` (adds `code` slug) and `validation-problem.model.yaml` (adds `errors[]` array). properties: title: type: string description: Short, human-readable summary of the problem. status: type: integer description: HTTP status code. minimum: 100 maximum: 599 detail: type: string description: >- Human-readable explanation specific to this occurrence. - type: object properties: code: type: string description: >- Stable, machine-readable error slug in the form `"."`. * `resource` is the camelCased domain — e.g. `sequence`, `contact`, `inboxThread`, `blacklistDomainRule`. * `variant` is the camelCased specific failure mode — e.g. `notFound`, `forbidden`, `duplicateName`, `globalRuleReadOnly`. Use `code` for programmatic error handling; use `detail` for user-facing messages. Slugs are stable across server-side enum reorderings and never change meaning under a given resource. pattern: ^[a-z][a-zA-Z0-9]*(\.[a-z][a-zA-Z0-9]*)+$ example: sequence.notFound title: Business Problem description: >- Domain error response carrying a stable, namespaced error slug. Emitted for most 4xx responses (business 400, 403, 404, 409, …) and for 503 when a downstream dependency is unavailable. - example: title: Forbidden status: 403 detail: You do not have permission to access this resource. code: sequence.forbidden example: title: Forbidden status: 403 detail: You do not have permission to manage searches. code: liveDataSearch.forbidden '404': description: Search not found, or already deleted content: application/problem+json: schema: allOf: - allOf: - type: object title: Problem Details description: >- Bare RFC 9457 problem-details envelope. Returned by middleware-level errors that don't carry domain context: 401 Unauthorized (auth middleware), 429 Too Many Requests (rate-limit middleware), and route-level 404 / 405 / 415 (framework middleware). Business and validation responses extend this envelope and add additional fields — see `business-problem.model.yaml` (adds `code` slug) and `validation-problem.model.yaml` (adds `errors[]` array). properties: title: type: string description: Short, human-readable summary of the problem. status: type: integer description: HTTP status code. minimum: 100 maximum: 599 detail: type: string description: >- Human-readable explanation specific to this occurrence. - type: object properties: code: type: string description: >- Stable, machine-readable error slug in the form `"."`. * `resource` is the camelCased domain — e.g. `sequence`, `contact`, `inboxThread`, `blacklistDomainRule`. * `variant` is the camelCased specific failure mode — e.g. `notFound`, `forbidden`, `duplicateName`, `globalRuleReadOnly`. Use `code` for programmatic error handling; use `detail` for user-facing messages. Slugs are stable across server-side enum reorderings and never change meaning under a given resource. pattern: ^[a-z][a-zA-Z0-9]*(\.[a-z][a-zA-Z0-9]*)+$ example: sequence.notFound title: Business Problem description: >- Domain error response carrying a stable, namespaced error slug. Emitted for most 4xx responses (business 400, 403, 404, 409, …) and for 503 when a downstream dependency is unavailable. - example: title: Not Found status: 404 detail: The requested resource was not found. code: sequence.notFound example: title: Not Found status: 404 detail: Live Data search 123 was not found. code: liveDataSearch.notFound '502': description: >- The search service answered with an error; the search is kept, try again content: application/problem+json: schema: allOf: - type: object title: Problem Details description: >- Bare RFC 9457 problem-details envelope. Returned by middleware-level errors that don't carry domain context: 401 Unauthorized (auth middleware), 429 Too Many Requests (rate-limit middleware), and route-level 404 / 405 / 415 (framework middleware). Business and validation responses extend this envelope and add additional fields — see `business-problem.model.yaml` (adds `code` slug) and `validation-problem.model.yaml` (adds `errors[]` array). properties: title: type: string description: Short, human-readable summary of the problem. status: type: integer description: HTTP status code. minimum: 100 maximum: 599 detail: type: string description: >- Human-readable explanation specific to this occurrence. - type: object properties: code: type: string description: >- Stable, machine-readable error slug in the form `"."`. * `resource` is the camelCased domain — e.g. `sequence`, `contact`, `inboxThread`, `blacklistDomainRule`. * `variant` is the camelCased specific failure mode — e.g. `notFound`, `forbidden`, `duplicateName`, `globalRuleReadOnly`. Use `code` for programmatic error handling; use `detail` for user-facing messages. Slugs are stable across server-side enum reorderings and never change meaning under a given resource. pattern: ^[a-z][a-zA-Z0-9]*(\.[a-z][a-zA-Z0-9]*)+$ example: sequence.notFound title: Business Problem description: >- Domain error response carrying a stable, namespaced error slug. Emitted for most 4xx responses (business 400, 403, 404, 409, …) and for 503 when a downstream dependency is unavailable. example: title: Bad Gateway status: 502 detail: 'Upstream service failure: ...' code: liveDataSearch.upstreamFailure components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- Authenticate every request with a Bearer token. Pass your Reply API key in the `Authorization` header: ``` Authorization: Bearer ``` Get your API key from the Reply dashboard: **Settings → API Key**. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.