Ctrlk
Go to SumbleBook a time
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Signals

Search Sumble Signals across the accounts available to your API key. Signals include champion movements, recent hires and promotions, technology and product mentions, projects and initiatives, and technology or job function trends.

Use this endpoint when you want a filtered feed across many accounts. If you already have one Sumble organization id, use Organization signals instead.

Use Priority Signals search when you want the AI-generated digest items from your Priority Signals feed, filtered by the signal, organization, person, or job post IDs attached to their source signals.

Search signals

Search by any combination of signal IDs, organization IDs, person IDs, technology slugs, job function names, priorities, and saved organization list IDs. The request body may be omitted; when present, all filter fields are optional. Filters are combined with AND; values inside each filter array are combined with OR.

curl https://api.sumble.com/v9/signals \
  --request POST \
  --header "Authorization: Bearer $API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "filter": {
      "signal_ids": [123],
      "organization_ids": [31],
      "person_ids": [12729201],
      "job_functions": ["Account Executive"],
      "priorities": ["high"],
      "account_list_ids": [4]
    }
  }'

To search people-movement signals by job function, omit technology_slugs unless the same signals also have matching technology metadata.

To search for signals about specific people, pass their Sumble person IDs in person_ids. This matches the person_id field returned on person-related signals.

Recency window

This endpoint returns only signals from the last 30 days, regardless of the other filters you apply. This keeps searches fast and focused on current activity.

The only exception is a direct lookup by signal_ids: those signals are always returned regardless of age.

Response

The response contains a signals array. Each signal includes signal_id, a display-ready title, display_type, and date, plus optional context such as subtitle, type, organization_name, organization_id, person_id, matched_technologies, location, job_function, priority, explanation, and sales_angle.

For person-movement signals, subtitle may include a normalized start-date label such as Started Jun 2026 or Starting Jul 2026.

Job-post signals (technology and product mentions, projects, and first mentions) also include suggested_contacts: the top contacts to consider reaching out to at the account, ranked by relevance. It contains a people array — each with person_id, name, title, linkedin_url, and a relevance score from 1 to 10 (higher is a stronger match) — and a sumble_url linking to all matching people for the job post.

Each signal also includes account_status: the CRM relationship between the signal's organization and your account (customer, prospect, or not_in_crm). Only populated when your account has a linked CRM seat (Salesforce or HubSpot); omitted otherwise.

Credit cost

1 credit per signal returned. Searches with no returned signals do not consume credits.

Search signals

post

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).

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body
Responses
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.

application/json
idstring · uuidRequired
credits_usedintegerRequired
credits_remainingintegerRequired
post/v9/signals

Search Priority Signals

Search your Priority Signals digest items by any combination of signal IDs, organization IDs, person IDs, and job post IDs. The request body may be omitted; when present, all filter fields are optional. Filters are combined with AND; values inside each filter array are combined with OR.

Priority Signals are AI-generated summaries of the highest-priority signals in your account feed. Each result includes the digest item headline and content, a URL to view the digest in Sumble, source signal_ids, and searchable organization_ids, person_ids, and job_post_ids derived from the source signals.

Response

The response contains a priority_signals array. Each priority signal includes url, signal_ids, headline, content, date, organization_ids, person_ids, and job_post_ids. The date is returned as YYYY-MM-DD.

Credit cost

1 credit per priority signal returned. Searches with no returned priority signals do not consume credits.

Search priority signals

post

Priority signals are AI-generated digest items summarizing the most important signals in a user's account feed. They optionally can be searched by signal, organization, person, or job post IDs attached to their source signals. Returns the most recent 20 priority signals based on the specified filters, or omit filters to simply return the latest.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body
Responses
200

Priority signals matching the requested filters. Charged one credit per priority signal returned.

application/json
idstring · uuidRequired
credits_usedintegerRequired
credits_remainingintegerRequired
post/v9/signals/priority
PreviousIntelligence endpointsNextIntelligence briefs

Last updated