Skip to main content
PATCH /v1/tenants/{product_slug}/scoring-config sets the Company Profile and Buyer Persona that drive lead scoring for your own tenant or a direct child tenant. Before this endpoint, these fields could only be set by hand in the dashboard, which meant a programmatically provisioned tenant scored every visitor against an empty ICP until someone logged in and filled it out. Call this right after Create Tenant — or pass the same fields as scoring_config on the create call itself — to make onboarding fully hands-off. Only fields you supply are changed. Omitted fields keep their current value — this is a partial update, not a full replace.

​
Endpoint

​
Path Parameter

​
string
required
Your own tenant’s slug, or a direct child tenant’s slug.

​
Request Body

All fields are optional. Send only the fields you want to change.
​
string
A new display name for the tenant (Company Profile).
​
string
A short category or industry label for the tenant’s own business (Company Profile).
​
string
A plain-English description of the tenant’s product or business (Company Profile). Also used to tune visitor identification accuracy.
​
string
URL to the tenant’s own LinkedIn company page (Company Profile).
​
string
A plain-English description of the tenant’s ideal buyer persona — title, seniority, department (e.g. "VP or Director of Engineering at a Series B+ SaaS company").
​
string
A plain-English description of the tenant’s ideal customer company — industry, size, market (e.g. "B2B SaaS companies selling to mid-market and enterprise buyers").
​
number
A value between 0 and 1 controlling how heavily Buyer Persona fit is weighted against company fit when scoring. Defaults to 0.5 the first time any persona field is set for a tenant with no prior ICP.
Supplying any of persona_description, company_description, or persona_weight creates an Ideal Customer Profile (ICP) for this tenant if one doesn’t already exist. name, category, overview, and linkedin_company_url write directly to the tenant’s Company Profile and take effect independently — you can update either group, or both, in the same request.

​
Example Request

​
Response

Returns the tenant’s full scoring configuration after the update, same shape as Get Scoring Config:

​
Required Scope

Requires tenants:write.

​
Error Responses