Score Contacts by Signal Activity
Score contacts by their active buying signals. Returns the aggregate Signal Score - a [0, 1] value - plus the active signal breakdown per contact.
Accepts up to 100 contacts. Each contact is resolved to a Lusha person ID and company ID server-side (identity only - no PII is revealed) before scoring. Provide one of:
id(encrypted Lusha contact ID)linkedinUrlemailfirstName+lastName+ (companyNameorcompanyDomain)
Each result is one of:
- A scored entry -
signalScore,signalTypes, andnoActiveSignals. - A
NOT_FOUNDentry - identity resolution failed for the supplied identifier. - A
NO_SCOREentry - the contact resolved, but the scoring engine returned nothing for it.
Note: A full outage of the identity-resolution provider is never masked as
NOT_FOUND- it returns a retryable502instead, so callers can retry rather than treating the batch as authoritatively unresolved.
Billing: 1 credit is charged per scored row via
signal_score_contact_reveal. This action is currently limited-availability - while it isn’t yet seeded on an account’s pricebook, the endpoint stays free (billing.creditsChargedis0). Error rows (NOT_FOUND/NO_SCORE) are never charged.
Authorizations
Your Lusha API key. You can find this in your Lusha dashboard under API settings.
Include this key in the api_key header for all requests.
Body
1 - 100 elements