Browse published operations

List the signal configs that decide which signals you receive -- their names, types, priorities, lookback windows, and filters, plus how many signals each has produced in the last 7 days and a link to its settings page. Read-only, and scoped exactly as the web app's signal settings page is: your own configs, your Sumble Enterprise account's shared configs, or your email domain's shared configs, whichever apply to you. Normal listings exclude deleted configs; an explicit ID lookup can return an authorized deleted config without a settings link. Free -- does not consume credits.

Unified jobs endpoint

Unified teams endpoint

Mark a priority signal (identified by its id from Search Priority Signals) as relevant or not relevant, or clear previously-set feedback by passing is_relevant: null. Mirrors the relevant / not relevant feedback available in the web app. Free -- does not consume credits.

Returns the job function and level for job titles. Send titles. Returns results with input, jobfunction and job level, plus matchedcount.

Look up projects by name

Look up technology categories by slug or name

Look up technologies by name, slug, or alias

Get organization signals

Returns an organization's tech stack grouped by business function and category, with evidence. Send organization_id.

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 suggestedcontacts: the top few people to consider reaching out to at the account, plus a link to view all of them. Each signal also carries accountstatus: the CRM relationship between the signal's organization and the calling account ('customer', 'prospect', or 'notincrm'). Only populated when the calling account has a linked CRM seat (Salesforce or HubSpot). Results are paginated with limit (default and maximum 100) and offset (default 0, maximum 10,000).

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 priority signals based on the specified filters, or omit filters to simply return the latest. Results are paginated with limit (default 20, maximum 100) and offset (default 0, maximum 10,000).

Find technologies by name

Find, match, and enrich people. Provide a people list (list mode) or a filter (search mode) and compose the response with select. On v7 and earlier this endpoint is synchronous: one call returns the people. On v8 and later it is asynchronous in both modes. Send a people or filter body to start a background job — the response returns a requestid and status: "pending", and no credits are charged yet (the request is validated and your balance pre-checked, so you still get a 400/402 up front). Then send { "requestid": "..." } to the same endpoint to poll: you get status pending/running until it finishes, then succeeded (with the full people/total result) or failed. Credits are charged once, on the first succeeded poll; repeat polls report creditsused: 0. The async response adds requestid and status fields.

Unified organizations endpoint. For a SINGLE known company, pass organizations (a list of {id} or {name/url/location} matchers, e.g. {"url": "stripe.com"} -- bare domain, no https:// prefix) -- NOT filter. filter.query is an advanced search DSL for finding organizations matching job/tech evidence (e.g. "technology EQ 'react'"), not a company lookup field, and a bare domain there returns a 400. select is always required (may be {} for id-only).

Retrieve the intelligence brief for an organization