Provided by Lusha
Get Hiring, Headcount, Traffic or News Signals for Lusha Company Ids (Lusha)
Get the latest event of one chosen signal type for up to ten companies named by their Lusha company id: a hiring surge, a headcount increase or decrease over 1 to 12 months, a web traffic or IT spend change, LinkedIn activity intent, or one news category. One signal type per call and one event per company, with an optional start date that keeps only newer events. A company without that signal is a miss and is not charged. Get the ids from Lusha company prospecting or lookalikes.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ids",
"signalType"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"maxLength": 200,
"minLength": 3
},
"maxItems": 10,
"minItems": 1
},
"startDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"signalType": {
"enum": [
"linkedinActivityIntent",
"websiteTrafficDecrease",
"websiteTrafficIncrease",
"itSpendIncrease",
"itSpendDecrease",
"surgeInHiring",
"headcountIncrease1m",
"headcountIncrease3m",
"headcountIncrease6m",
"headcountIncrease12m",
"headcountDecrease1m",
"headcountDecrease3m",
"headcountDecrease6m",
"headcountDecrease12m",
"surgeInHiringByDepartment",
"surgeInHiringByLocation",
"riskNews",
"commercialActivityNews",
"corporateStrategyNews",
"financialEventsNews",
"peopleNews",
"marketIntelligenceNews",
"productActivityNews"
],
"type": "string"
}
},
"additionalProperties": false
}{
"ids": [
"v1.q8t17e2kTtF85tpUxIuAon7QWRaHpriT"
],
"signalType": "headcountIncrease3m"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the Lusha Endpoint /v3/companies/signals on Glasser with input {"ids":["v1.q8t17e2kTtF85tpUxIuAon7QWRaHpriT"],"signalType":"headcountIncrease3m"}glasser run -p lusha -e '/v3/companies/signals' -i '{"ids":["v1.q8t17e2kTtF85tpUxIuAon7QWRaHpriT"],"signalType":"headcountIncrease3m"}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"lusha","endpoint":"/v3/companies/signals","input":{"ids":["v1.q8t17e2kTtF85tpUxIuAon7QWRaHpriT"],"signalType":"headcountIncrease3m"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |