The lead scoring API is a beta at version 2026-09-beta and needs a Professional subscription or higher.
Source pending
Another fact disagrees with this one: The lead scoring API answers at /marketing/lead-scoring/2027-03-beta/scores, and only after the portal opts into the beta: before that, every call returns 403 LEAD_SCORING_PUBLIC_API_NOT_ENABLED.
More facts from this area
- A score criterion counting events on associated records uses
{type: ASSOCIATION_UE, associatedObjectTypeId, associationSpec, inverseAssociationSpec, rollupType: SUM, associationFilters: {propertyFilters: [...]}, recordCalculation: {type: MULTI_UE, eventCalculators: [...]}}.Measured PUT …/scores/{id}/draftreplaces the whole draft and can only override outputs that already exist. A published score has no draft:GET …/scores/{id}/draftreturns 404DRAFT_NOT_FOUND.Measured- An event criterion built by API as
MULTIofCONDITIONALs scores but the score editor shows "We couldn't load your criterion"; the editor-compatible form is oneeventCalculatorsentry per criterion withrecordCalculation: {type: MATCH, property, matchRules: [...]}.Measured - A lead score property rule must be a top-level
MULTIofCONDITIONALcalculators whosewhereConditionis aCOMPOSITEAND ofSINGLEconditions. A bareCONDITIONALorMATCHat the top returnsINVALID_TOP_LEVEL_CALCULATOR_TYPE.Measured - HubSpot appends a numeric suffix to a lead score's output property names (for example
<name>_total_<number>), so the names must be read back after the score is created.Measured
Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]