---
title: "Search signals"
method: POST
path: "/v9/signals"
tags: ["signals"]
---

# Search signals

`POST /v9/signals`

Signals are sales-relevant events such as champion job changes, recent hires and promotions, technology and product mentions, projects and initiatives, and technology and job-function trends. Job-post signals (technology and product mentions, projects, and first mentions) also include `suggested_contacts`: the top few people to consider reaching out to at the account, plus a link to view all of them. Each signal also carries `account_status`: the CRM relationship between the signal's organization and the calling account ('customer', 'prospect', or 'not_in_crm'). Only populated when the calling account has a linked CRM seat (Salesforce or HubSpot).

## Request body

- SearchSignalsRequest
  - `filter` SearchSignalsFilter
    - `organization_ids` integer[], nullable — Organization IDs to filter signals by.
    - `person_ids` integer[], nullable — Sumble person IDs to filter signals by.
    - `signal_ids` integer[], nullable — Signal IDs to filter signals by.
    - `technology_slugs` string[], nullable — Canonical technology slugs to filter signals by, such as `kubernetes` or `salesforce`.
    - `job_functions` string[], nullable — Job function names to filter signals by, such as `Engineering` or `Sales`.
    - `priorities` string[], nullable — Priorities to filter signals by. Matches the `priority` field returned on each signal.
    - `account_list_ids` integer[], nullable — Account list IDs to filter signals to accounts in those lists.

## Response `200`

Signals matching the requested filters. Charged one credit per signal returned. Job-post signals also carry `suggested_contacts` with the top contacts to consider and a link to view all.

- SignalsResponse
  - `id` string, uuid, required
  - `credits_used` integer, required
  - `credits_remaining` integer, required
  - `signals` Signal[], required
    - `signal_id` integer, nullable
    - `title` string, required
    - `subtitle` string, nullable
    - `explanation` string, nullable
    - `sales_angle` string, nullable
    - `date` string, date-time, required
    - `sumble_url` string, nullable
    - `display_type` string, required
    - `type` string, nullable
    - `matched_technologies` SignalTechnology[], nullable
      - `name` string, required
      - `slug` string, required
      - `label` string, nullable
    - `organization_name` string, nullable
    - `organization_id` integer, nullable
    - `job_post_id` integer, nullable
    - `person_id` integer, nullable
    - `linkedin_url` string, nullable
    - `location` string, nullable
    - `job_function` string, nullable
    - `priority` string, nullable
    - `suggested_contacts` SuggestedContacts
      - `people` SuggestedContact[], required
        - `person_id` integer, nullable
        - `name` string, nullable
        - `title` string, nullable
        - `linkedin_url` string, nullable
        - `score` number, nullable
      - `sumble_url` string, nullable
    - `account_status` 'customer' | 'prospect' | 'not_in_crm', nullable — CRM relationship between the signal's organization and the calling account: 'customer' (a customer account in the calling account's CRM), 'prospect' (tracked in CRM but not a customer), or 'not_in_crm' (no CRM record). Only populated when the calling account has a linked CRM seat (Salesforce or HubSpot); omitted otherwise, even when requested.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/sumble/apis/sumble-api.md) · [All operations](https://skmtc.net/sumble/apis/sumble-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sumble/sumble-api/revisions/fbfd97abec00/schema)