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.
How to run it
Step 1Set up
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.md
Show me how to use the Lusha endpoint /v3/contacts/signals on Glasser.glasser run -p lusha -e '/v3/contacts/signals' -i '{"ids":["v1.XxBjwQixVmRjDOmVoSo30QDZV5iYqLNtcg"],"signalType":"companyChange"}' --endpoint-version 1Uses endpoint version 1. Inspect the current price before running. 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. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to plan which events to research, you might look for entries relevant to your topic and consider why each one fits.
Copy this prompt into your agent to find relevant events in the returned data.
Use lusha:/v3/contacts/signals on Glasser.
Find events relevant to my topic in the returned data and explain why each matches.Endpoint structure
{
"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 pricing works
| Per result returned | Charged for each result returned. No charge when no data is returned. | $0.1248 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $3.00 |
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |