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

# Create a saved search

> Keeps a search's `filters` under a `title`, for people (the default) or for companies. To keep a search you ran, send the `filters` its page answered with.

Run a saved people search with `POST /v1/saved-searches/{savedSearchId}/run`, or any saved search as `savedSearchId` in a search or a count.

Free. **Scope:** search, with a key that can write.



## OpenAPI

````yaml /openapi.json post /v1/saved-searches
openapi: 3.1.0
info:
  title: outbound.dev API
  version: v1
  description: Find people and companies, and see what every call costs, with one API key.
servers:
  - url: https://api.outbound.dev
security: []
tags:
  - name: People
    description: >-
      Search people with filters, a saved search or a plain-language query,
      count matches and look up filter values.
  - name: Companies
    description: >-
      Search companies, count matches, name one company by its name, domain or
      LinkedIn page, and list its people.
  - name: Saved searches
    description: Keep a search under a title and run it again, for people or for companies.
  - name: Jobs
    description: >-
      Long tasks a call started: their progress, what they produced and what
      they were charged.
  - name: Account
    description: >-
      The calling key and its organization, its rate limits, and revoking the
      key.
  - name: Billing
    description: The balance, the ledger of every change to it, and the price list.
  - name: Usage and requests
    description: >-
      Calls and spend by day, and the record of every request of the last 30
      days.
paths:
  /v1/saved-searches:
    post:
      tags:
        - Saved searches
      summary: Create a saved search
      description: >-
        Keeps a search's `filters` under a `title`, for people (the default) or
        for companies. To keep a search you ran, send the `filters` its page
        answered with.


        Run a saved people search with `POST
        /v1/saved-searches/{savedSearchId}/run`, or any saved search as
        `savedSearchId` in a search or a count.


        Free. **Scope:** search, with a key that can write.
      operationId: postSavedSearches
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                title:
                  type: string
                  description: >-
                    The saved search's title. Titles need not be unique, but a
                    shared title cannot be run by name.
                  minLength: 1
                  maxLength: 255
                  example: Portugal freight ops
                type:
                  type: string
                  description: >-
                    The kind of search the filters are for. It cannot change
                    later.
                  enum:
                    - people
                    - company
                  default: people
                filters:
                  type: object
                  description: >-
                    The search's filters, as the people or company search takes
                    them, such as the `filters` a search page answered with.
                  maxProperties: 100
                  additionalProperties: {}
                  example:
                    job_title_levels:
                      - director
                    job_title_role:
                      - operations
              required:
                - title
                - filters
            example:
              title: Portugal freight ops
              filters:
                job_title_levels:
                  - director
                job_title_role:
                  - operations
      responses:
        '201':
          description: The saved search.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/RequestId'
            X-Charged-Usd:
              $ref: '#/components/headers/ChargedUsd'
            X-Balance-Usd:
              $ref: '#/components/headers/BalanceUsd'
            RateLimit-Limit:
              $ref: '#/components/headers/RateLimitLimit'
            RateLimit-Remaining:
              $ref: '#/components/headers/RateLimitRemaining'
            RateLimit-Reset:
              $ref: '#/components/headers/RateLimitReset'
          content:
            application/json:
              schema:
                type: object
                required:
                  - id
                  - title
                  - type
                  - filters
                  - createdAt
                properties:
                  id:
                    type: string
                  title:
                    type: string
                  type:
                    type: string
                    enum:
                      - people
                      - company
                    description: The kind of search the filters are for.
                  filters:
                    type: object
                    additionalProperties: true
                  ignoredFilterKeys:
                    type: array
                    items:
                      type: string
                    description: >-
                      Stored filters the search no longer takes, which are left
                      out when it runs.
                  createdAt:
                    type: string
                    format: date-time
                  updatedAt:
                    type: string
                    format: date-time
                    description: Absent until it is first changed.
              example:
                id: 6a1f0c2b9d4e8a7f3c5b2e15
                title: Portugal freight ops
                type: people
                filters:
                  job_title_levels:
                    - director
                  job_title_role:
                    - operations
                ignoredFilterKeys: []
                createdAt: '2026-11-14T10:05:00.000Z'
        '429':
          $ref: '#/components/responses/RateLimited'
        4XX:
          $ref: '#/components/responses/Error'
        5XX:
          $ref: '#/components/responses/ServerError'
      security:
        - apiKey: []
components:
  headers:
    RequestId:
      description: The request's id. Quote it when you write to support.
      schema:
        type: string
        example: req_6a1f0c2b9d4e8a7f3c5b2e10
    ChargedUsd:
      description: What this call cost, in US dollars as an exact six-decimal string.
      schema:
        type: string
        example: '0.000500'
    BalanceUsd:
      description: >-
        The organization's balance after this call, in US dollars as an exact
        six-decimal string.
      schema:
        type: string
        example: '9.999500'
    RateLimitLimit:
      description: >-
        The calls allowed in the window of the route's limit with the fewest
        calls left.
      schema:
        type: integer
        example: 20
    RateLimitRemaining:
      description: The calls left in that window.
      schema:
        type: integer
        example: 19
    RateLimitReset:
      description: Seconds until that window resets.
      schema:
        type: integer
        example: 42
    RetryAfter:
      description: Seconds to wait before calling again.
      schema:
        type: integer
        example: 42
  responses:
    RateLimited:
      description: >-
        Too many calls. Wait the seconds in Retry-After, then call again. The
        body is empty.
      headers:
        Retry-After:
          $ref: '#/components/headers/RetryAfter'
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
        RateLimit-Limit:
          $ref: '#/components/headers/RateLimitLimit'
        RateLimit-Remaining:
          $ref: '#/components/headers/RateLimitRemaining'
        RateLimit-Reset:
          $ref: '#/components/headers/RateLimitReset'
    Error:
      description: The request was refused. The body names the reason in `error.code`.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ServerError:
      description: >-
        Something failed on our side and nothing was charged. Retry with
        backoff; quote X-Request-Id if it persists. The body is empty.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - doc_url
          properties:
            code:
              type: string
              description: >-
                Stable and machine-readable: branch on it. It never changes
                meaning.
            message:
              type: string
              description: >-
                A human-readable explanation for logs. It may be reworded at any
                time.
            param:
              type: string
              description: The request field the error is about, when there is one.
            doc_url:
              type: string
              description: The code's entry in the errors reference.
            request_id:
              type: string
              description: >-
                The request's id, as in the X-Request-Id header. Quote it to
                support.
      example:
        error:
          code: insufficient_balance
          message: Your balance cannot cover this call. Add funds and try again.
          doc_url: https://outbound.dev/docs/errors#insufficient_balance
          request_id: req_6a1f0c2b9d4e8a7f3c5b2e10
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        An API key from the console, starting `ob_live_`, sent as
        `Authorization: Bearer <key>`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.