Get Sales Signal taxonomy and discovery schemas

Developer keys need signals:read, or the complete legacy combination of companies:read. 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.

The response keeps taxonomy_version and canonical signal_types, plus billing and discovery. The example abbreviates taxonomy entries and criteria schemas for readability; consume each full criteriaSchema returned by the selected server.

discovery.sources contains jobs, linkedin_posts and job_changes. Each entry has source, label, supportedFrequencies, defaultFrequency and criteriaSchema derived from the owning source contract. Jobs defaults daily; posts defaults daily and can run hourly; Job changes defaults weekly and supports daily/weekly only. discovery.industriesEndpoint points to the free canonical lookup. Job changes uses industry labels; post criteria uses numeric industry IDs. LinkedIn posts accept either keywordPhrases or keywords. Added phrases become one quoted OR query; when the list is present, it determines keywords. Industry and author-profile filters apply to the whole query. Use the returned full schema and the create reference for validation details. Hourly controls check cadence; LinkedIn discovery does not expose a posted-date or lookback input.

Read pricing under billing.sources[source], with enabled, creditsPerSignal and policyVersion. Job changes is 2 organization credits per new unique delivered Signal; jobs/posts are 0.2. Duplicate delivery and free count previews do not charge again. An explicitly purchased Job changes sample can charge up to 2 credits even when company filters exclude that candidate; inspect preview creditsUsed. The top-level Company billing rate/flag is a different policy and must not replace the source-specific rate.

This read performs no provider search and costs no credits. It describes supported source contracts and configured policy; it does not prove provider readiness, successful collection, or production deployment. Compare deployed capabilities and handle source-unavailable errors when executing. Saved-Company enrollment uses its own monitoring contract.

Jobs supports providerSelection="automatic" for compatible-source routing. Job changes titles are optional with a selected department/seniority; maxCandidates and maxCreditsPerCheck are optional positive whole numbers, and omission/null removes the user-set cap. A complete source schema is the authority for defaults and validation.

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.