Provided by Apollo
Match up to 10 People by LinkedIn URL, Email or Name and Employer (Apollo)
Match up to 10 known people in one call, each identified by a LinkedIn URL, an email address, or a name together with an employer domain or employer name. Every matched person comes back as one Apollo record with demographics, employment and business contact data; an entry Apollo cannot match comes back empty and is not charged.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"details"
],
"properties": {
"details": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"email": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"domain": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"last_name": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"first_name": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"linkedin_url": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"organization_name": {
"type": "string",
"maxLength": 500,
"minLength": 1
}
},
"additionalProperties": false
},
"maxItems": 10,
"minItems": 1
}
},
"additionalProperties": false
}{
"details": [
{
"linkedin_url": "https://www.linkedin.com/in/johncollison"
},
{
"name": "Jane Doe",
"domain": "example.com"
}
]
}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 Apollo Endpoint /api/v1/people/bulk_match on Glasser with input {"details":[{"linkedin_url":"https://www.linkedin.com/in/johncollison"},{"name":"Jane Doe","domain":"example.com"}]}glasser run -p apollo -e '/api/v1/people/bulk_match' -i '{"details":[{"linkedin_url":"https://www.linkedin.com/in/johncollison"},{"name":"Jane Doe","domain":"example.com"}]}' --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":"apollo","endpoint":"/api/v1/people/bulk_match","input":{"details":[{"linkedin_url":"https://www.linkedin.com/in/johncollison"},{"name":"Jane Doe","domain":"example.com"}]},"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 |