API v3 is live and in beta: expect possible malfunctions and breaking changes in the coming days. If you find a bug, please report it to your Sillage contact.
APIv3Signal TemplatesParameters by template

Hiring for roles my product serves

Parameters, defaults and rules of the "Hiring for roles my product serves" signal template.

Spot companies hiring for the roles your product serves: they are building the team you sell to. The job titles are matched against the title of each job offer.

Keyhiring-for-roles-my-product-serves
Categorypeople
Watchescompany
Setupsaccount monitoring only

Set this signal up with POST /v3/signal-setups: send the template's id as signal_template_id and the parameters below in parameters. Its id is in List signal templates. Any parameter not listed here is refused with a 422.

Parameters

ParameterTypeRequiredAllowed valuesDefaultDescription
scopesarray of stringYesaccount_monitoring (at least one)—Where the signal looks. Only account monitoring is available.
use_persona_job_titlesbooleanNotrue, falsetrueWhether to also use the job titles of your persona, read at each run.
job_titlesarray of stringNoJob titles[]The job titles to look for, on top of the persona's when use_persona_job_titles is true.

Default is what the server stores when you leave the parameter out. — means there is no default: the parameter is required, or it is simply not set.

Rules

  • This signal supports account monitoring only. Discovery is refused.
  • When you leave use_persona_job_titles out, it is true. The persona's job titles are read at each run, never copied into the setup, so the signal follows any later change to the persona.
  • With one persona and no persona_id, the setup is tied to your persona, so a persona you add later never changes the job titles it reads.
  • The titles you send in job_titles are added to the persona's. To look only for your own titles, send use_persona_job_titles: false.
  • With several personas, send persona_id when use_persona_job_titles is true or left out: without it the request is refused with 422, and errors names persona_id.
  • A persona is needed only when use_persona_job_titles is true. Send false with your own job titles otherwise.

Errors

A parameter that is missing, of the wrong type, or not an allowed value is refused with a 422 that names it under errors, for example parameters.scopes. These errors are specific to this signal template:

StatusCause
422parameters.scopes contains discovery. Only account_monitoring is allowed.
422parameters.job_titles is empty, use_persona_job_titles is true and your persona has no job title. Add job_titles, or add a job title to the persona first.
422parameters.job_titles is empty while use_persona_job_titles is false. Send at least one job title.
409The signal template is archived.

Example

parameters of a setup:

{
  "scopes": ["account_monitoring"],
  "use_persona_job_titles": true,
  "job_titles": ["Head of Sales"]
}

On this page