Create a discovery monitor

Developer keys need signals:read and signals:run and signals:write, or the complete legacy combination of companies:read and companies:write and leads:read and search:run. Signals scopes do not grant general CRM or Search access.

This reference describes the Signals discovery-monitor contract. Check the selected server’s capabilities and Signals catalog for supported sources, criteria, cadences and current billing. API availability does not enable monitoring or establish provider readiness, completed collection or delivered Signals.

HTTP 201 confirms saved configuration and any returned queued-run receipt; it does not mean provider collection or paid delivery has finished. The default enabled=true and runNow=true starts the first asynchronous check. Set runNow=false to wait for the recurring cadence, or enabled=false to save paused configuration with no run. The result always includes monitor and nullable run.

Discovery is independent of saved-Company enrollment. Choose exactly one immutable source per monitor. Use the catalog’s source criteriaSchema, supportedFrequencies and defaultFrequency; explicit frequency is recommended. Job changes defaults weekly; jobs/posts default daily. Hourly is supported only for LinkedIn posts.

Job changes

Roles are custom phrases, not a fixed position list. The source searches new roles, then verifies required employer industry, actual size, HQ country and person-country evidence. Missing or incompatible required evidence is withheld with warnings; seller fit tags do not replace verified industry. Daily uses the source date window for the last day; weekly uses its last-seven-day date window. Event dates can differ.

At least one role, department or seniority must be selected; title phrases are optional. Omit or send null for maxCandidates and maxCreditsPerCheck to collect all available candidates within organization credits. Either optional cap accepts strict positive whole numbers, with no fixed five-candidate maximum. The runtime freezes an affordable raw-candidate allowance and resumes bounded provider activities until source exhaustion or that allowance/cap. Invalid, duplicate or excluded candidates consume acquisition allowance. Delivery costs 2 organization credits per new unique job-change Signal. Duplicate organization delivery is free. Configuration itself is free; the default first check can deliver paid Signals. A Job change creates saved Signals, not Leads; Save person is a separate explicit operation.

LinkedIn posts

Use criteria.keywordPhrases for added keywords or phrases. The server normalizes the list and searches for any phrase with one quoted OR query, for example "outbound sales" OR "pipeline generation" OR "sales development". Industry and author-profile filters apply to that whole query. A list of terms does not create separate monitors or one search per term. For an existing raw Boolean query, send keywords without keywordPhrases; the raw query is preserved. If both are sent, the phrase list determines keywords.

Read industry options and use numeric IDs for authorsIndustryId. The following create request searches post text for any of three phrases, with the same Software Development and author-profile filters applied to all three:

{
  "name": "Outbound sales conversations",
  "source": "linkedin_posts",
  "criteria": {
    "keywordPhrases": [
      "outbound sales",
      "pipeline generation",
      "sales development"
    ],
    "authorsIndustryId": "4",
    "authorKeywords": "RevOps",
    "excludePromotions": true
  },
  "frequency": "hourly",
  "enabled": true,
  "runNow": true,
  "requestId": "linkedin-post-monitor-example-1"
}

Hourly sets the check cadence; it does not apply a last-hour post filter. The current LinkedIn post discovery criteria do not expose a posted-date or lookback field. The feed’s window_days filters saved evidence when reading it; it does not change what a monitor collects.

Post relevance is inferred automatically from the search intent and available organization context. Search intent stays primary; organization context can clarify relevance but cannot override it. Omit the legacy topic and relevanceMode fields in new requests.

Job openings and collection coverage

Jobs and LinkedIn posts retain all valid matches in batches and cost 0.2 credit per new unique delivered job/post. Duplicate deliveries do not incur another application delivery charge. No application delivery credits are charged for jobs/posts previews; provider acquisition costs are separate. Use criteria.providerSelection="automatic" to select the sources that enforce every active jobs filter; the wizard uses this mode without a provider list. Unsupported combinations fail instead of dropping filters. Explicit manual provider lists remain compatible; new monitor requests without a source plan use automatic routing. A blank job query is allowed only for jobType="remote"; remote-only acquisition retains explicit provider remote evidence. A jobs search market is not Company HQ geography. Read the full schemas from the catalog.

Omit maxResults: it is accepted only for compatibility and does not cap collection. Jobs/posts continue across provider pages in resumable batches; a processing batch is not an overall result limit. Job changes uses its own criteria.maxCandidates and credit limit. Source availability, provider coverage or credit holds can prevent complete collection; inspect collectionStatus and warnings. Saving a monitor, seeing an active state or receiving a queued run is not proof of delivery.

Reuse requestId after an uncertain create response with the same source, criteria, name, cadence and flags. A different payload using that ID returns 409. There is a maximum of 500 saved discovery monitors per organization/runtime. Poll monitor status, then read the saved feed with monitor_id; do not poll a discovery ID through the company-subscription run endpoint.

Compatibility: older API payloads may contain qualificationText, post topic or relevanceMode fields. These are legacy fields rather than current monitor inputs; omit them in new requests. Non-empty Job changes qualificationText is rejected.

Command Center can prepare a native approval plan with create_signal_discovery_monitor for this same command. Approval describes the saved configuration and any initial or recurring paid collection. The selected runtime must expose that native binding; API availability alone does not establish it. CLI source 0.2.126 adds autotouch signals create-discovery-monitor --data-file monitor.json, or named flags including --criteria-json. Omit enabled/runNow to retain server defaults, or explicitly use --no-enabled/--no-run-now. Inspect the installed CLI version; source support, package publication and backend deployment are separate.

Job monitor windows and employment types

For source=jobs, frequency=daily is the default and selects a past-day search; weekly selects the past seven days. The same window applies to preview, create, update and fresh scheduled checks. Omit the deprecated datePosted and linkedinDateRestrict inputs: they do not override monitor frequency.

Automatic routing can use Indeed, Google Jobs and LinkedIn when the other filters are compatible. Google Jobs uses its native posting-date filter. LinkedIn uses Scrappa’s Google-based search-date restriction, which is not an independently verified job-posting cutoff. Indeed checks returned posting dates before preview or delivery and excludes old, future, missing or unreadable dates; first-seen time never substitutes for posting time. Indeed requests date sorting unless another sort was saved, and still pages past old rows within bounded batches. Glassdoor has no supported lookback and is excluded from automatic date-window searches.

Omit jobType or use an empty string for Any job type. Current filters are part_time, contract, internship and remote. Legacy full_time/fulltime values are unrestricted. Paid continuation batches keep their saved search, date bounds and cursors; fresh checks use the current cadence. Selected-server deployment is separate from CLI 0.2.127 and these source-contract docs; inspect its catalog before relying on new behavior.

For source=fda, send frequency=weekly or omit it; daily and hourly are rejected. FDA activity monitors deliver free regulatory_action Signals for device, drug and food recalls, 510(k) clearances, PMA approvals and supplements, drug approvals and FDA warning letters. See the discovery guide for criteria.

For source=sec_filings, send frequency=daily or weekly (default weekly). SEC filings monitors deliver free Signals for Form D private offerings, 8-K executive changes, completed acquisitions and material agreements, and S-1/F-1 IPO registrations.