> ## Documentation Index
> Fetch the complete documentation index at: https://api.tryspecter.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete search

> Permanently deletes a saved search and all its associated data.

<Note> Free. This call does not consume credits. </Note>

## What you need

A saved search ID shared with the API; get one from [Get all saved searches](/api-reference/saved-searches/get-all-saved-searches).

## Behaviour

- The search must be shared with the API.
- `searchId` must be a number, otherwise `400`.
- Returns `404` if the search doesn't exist.
- This action cannot be undone; deleting removes the search from users' saved searches.

## What you do next

- **Confirm what's left.** Check your remaining searches with [Get all saved searches](/api-reference/saved-searches/get-all-saved-searches).




## OpenAPI

````yaml /api-ref/bundle_api.yaml delete /searches/{searchId}
openapi: 3.0.0
info:
  title: Specter API
  termsOfService: https://tryspecter.com/terms/
  contact:
    name: API support
    email: api-support@tryspecter.com
  version: 1.0.0
servers:
  - description: Production
    url: https://app.tryspecter.com/api/v1
security:
  - ApiKeyAuth: []
tags:
  - name: Enrich
    description: >
      Look up a company, person, or investor and, if Specter does not already
      hold it, fetch it on demand. Includes email-based person enrichment.
  - name: Search
    description: |
      Find records across every product from a single plain-English query.
  - name: Companies
    description: >
      Company profiles, funding, headcount, traction, the per-company signals
      and sub-resources attached to a single company, and identifier resolution.
  - name: People
    description: >
      Specter people records: profile data, contact details, and per-person
      lookups for a known person ID.
  - name: Investors
    description: >
      Specter investor records: profile, activity, targeting, funds, portfolio
      companies, and the funding rounds they have participated in.
  - name: Transactions
    description: |
      Transaction detail by ID: funding rounds, acquisitions, and IPOs.
  - name: News Signals
    description: |
      Company-level news signals: by ID, and for a saved list or company search.
  - name: Revenue Signals
    description: >
      Revenue and profitability signals: by ID, by date, and for a saved list or
      company search.
  - name: Talent Signals
    description: |
      Talent signals: by ID and in bulk by ID.
  - name: Investor Interest Signals
    description: |
      Investor interest signals: by ID and in bulk by ID.
  - name: Company Lists
    description: |
      Create, query, and maintain lists of companies, including their results.
  - name: Investor Lists
    description: |
      Create, query, and maintain lists of investors, including their results.
  - name: People Lists
    description: |
      Create, query, and maintain lists of people, including their results.
  - name: Saved Searches
    description: |
      List and delete searches saved via tryspecter.com.
  - name: Company Saved Searches
    description: |
      Details and results for saved company searches.
  - name: People Saved Searches
    description: |
      Details and results for saved people searches.
  - name: Investor Saved Searches
    description: |
      Details and results for saved investor searches.
  - name: Talent Signals Saved Searches
    description: |
      Details and results for saved Talent Signals searches.
  - name: Investor Interest Saved Searches
    description: |
      Details and results for saved Investor Interest Signals searches.
  - name: Network
    description: >
      Your team's LinkedIn network: the people and companies your teammates are
      connected to, and your reach into a given company.
  - name: Account
    description: >
      Organisation-level resources: your team's members, API call logs, and
      credit balance.
paths:
  /searches/{searchId}:
    delete:
      tags:
        - Saved Searches
      summary: Delete search
      description: >
        Permanently deletes a saved search and all its associated data.


        <Note> Free. This call does not consume credits. </Note>


        ## What you need


        A saved search ID shared with the API; get one from [Get all saved
        searches](/api-reference/saved-searches/get-all-saved-searches).


        ## Behaviour


        - The search must be shared with the API.

        - `searchId` must be a number, otherwise `400`.

        - Returns `404` if the search doesn't exist.

        - This action cannot be undone; deleting removes the search from users'
        saved searches.


        ## What you do next


        - **Confirm what's left.** Check your remaining searches with [Get all
        saved searches](/api-reference/saved-searches/get-all-saved-searches).
      parameters:
        - $ref: '#/components/parameters/SearchId'
      responses:
        '200':
          description: Ok
        '400':
          description: BadRequest
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SearchIdBadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          description: The search does not exist
components:
  parameters:
    SearchId:
      in: path
      name: searchId
      schema:
        type: integer
      required: true
      description: The ID of the saved search being requested.
  schemas:
    SearchIdBadRequest:
      properties:
        errorCode:
          type: string
          description: BAD_SEARCH_ID_TYPE
          example: BAD_SEARCH_ID_TYPE
        message:
          type: string
          description: The search id needs to be a number.
          example: The search id needs to be a number.
    ApiKeyMissing:
      properties:
        errorCode:
          description: API_KEY_MISSING
          example: API_KEY_MISSING
          type: string
        message:
          description: No API Key was presented on the header X-API-KEY
          example: No API Key was presented on the header X-API-KEY
          type: string
    ApiKeyNotValid:
      properties:
        errorCode:
          description: API_KEY_NOT_VALID
          example: API_KEY_NOT_VALID
          type: string
        message:
          description: API key present, but not valid
          example: API key present, but not valid
          type: string
  responses:
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/ApiKeyMissing'
              - $ref: '#/components/schemas/ApiKeyNotValid'
    Forbidden:
      description: Forbidden - There is no permissions to use the endpoint
      content:
        application/json:
          schema:
            type: object
            properties:
              errorCode:
                description: NOT_PERMITTED
                type: string
                example: NOT_PERMITTED
              message:
                type: string
                description: You do not have permission to access this resource.
                example: You do not have permission to access this resource.
            required:
              - errorCode
              - message
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key

````