# Search Contact Signals

Search for contact signals using identifiers like LinkedIn URL, email, or name + company.
This endpoint combines search and signal enrichment in a single request.

: 


Each contact can be identified by:
- Contact ID
- LinkedIn URL
- Email address
- Full name + Company (name or domain)


- Returns signals from the last 6 months by default
- Contacts are matched based on provided identifiers
- Returns both contact data and associated signals


Endpoint: POST /api/signals/contacts/search
Security: ApiKeyAuth

## Request fields (application/json):

  - `contacts` (array, required)
    List of contact identifiers to search for

  - `contacts.id` (string, required)
    A unique sequential ID to associate with the contact object in the API response
    Example: "12345"

  - `contacts.social_link` (string)
    LinkedIn profile URL
    Example: "https://www.linkedin.com/in/ron-nabet"

  - `contacts.full_name` (string)
    Full name of the contact
    Example: "Ron Nabet"

  - `contacts.email` (string)
    Email address
    Example: "dustin@lusha.com"

  - `contacts.companies` (array)
    Company associations

  - `contacts.companies.name` (string, required)
    Company name
    Example: "Lusha"

  - `contacts.companies.domain` (string, required)
    Company domain (FQDN, not URL)
    Example: "lusha.com"

  - `contacts.companies.is_current` (boolean)
    Whether this is the current company
    Example: true

  - `signals` (array, required)
    Types of signals to retrieve
    Enum: "allSignals", "promotion", "companyChange"

  - `startDate` (string)
    Start date for signal retrieval (YYYY-MM-DD format)
    Example: "2025-03-01"

## Response 200 fields (application/json):

  - `contacts` (object)
    Map of contact IDs to their signals

  - `endDate` (string)
    End date of the signal period
    Example: "2025-07-31"

  - `startDate` (string)
    Start date of the signal period
    Example: "2025-03-01"

  - `creditCharged` (integer)
    Number of credits charged for this request
    Example: 2

## Response 400 fields (application/json):

  - `error` (object, required)

  - `error.code` (integer, required)
    HTTP status code

  - `error.message` (string, required)
    Error message

## Response 401 fields (application/json):

  - `error` (object, required)

  - `error.code` (integer, required)
    HTTP status code

  - `error.message` (string, required)
    Error message

## Response 403 fields (application/json):

  - `error` (object, required)

  - `error.code` (integer, required)
    HTTP status code

  - `error.message` (string, required)
    Error message

## Response 429 fields (application/json):

  - `error` (object, required)

  - `error.code` (integer, required)
    HTTP status code

  - `error.message` (string, required)
    Error message