Provided by Lusha
Contact Signal Events by Lusha Id
The latest company-change or promotion event for up to ten people identified by Lusha contact id: for a company change, the previous and current employer with domains, the new title, department and seniority and the signal date. One event per contact per call; a contact without that signal is a miss and is not charged. Get ids from Lusha contact 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": [
"companyChange",
"promotion"
],
"type": "string"
}
},
"additionalProperties": false
}{
"ids": [
"v1.XxBjwQixVmRjDOmVoSo30QDZV5iYqLNtcg"
],
"signalType": "companyChange"
}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/contacts/signals on Glasser with input {"ids":["v1.XxBjwQixVmRjDOmVoSo30QDZV5iYqLNtcg"],"signalType":"companyChange"}glasser run -p lusha -e '/v3/contacts/signals' -i '{"ids":["v1.XxBjwQixVmRjDOmVoSo30QDZV5iYqLNtcg"],"signalType":"companyChange"}' --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/contacts/signals","input":{"ids":["v1.XxBjwQixVmRjDOmVoSo30QDZV5iYqLNtcg"],"signalType":"companyChange"},"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 |