Trigger a pipeline run (scoped to 1, some, or all records)
Submit a pipeline run. Returns immediately with job_id for polling.
Scoping the run (1/some/all):
- One record — pass entity_id as a single UUID or GLID (e.g. "GL-CO-00042")
- N specific records — pass entity_id as a comma/space/newline-separated list of UUIDs or GLIDs (e.g. "GL-CO-1, GL-CO-2, GL-FL-99")
- A previously-stamped batch — pass batch_id (UUID)
- A filter expression — pass filters (same shape as /leads/browse)
- The exact entity set of a previous run — pass manifest_id (UUID from GET /jobs/{id}/results); the recovery gesture for re-running a failed run
- All records in a state — pass none of the above
Mutually exclusive: pick at most one of entity_id, batch_id, filters, manifest_id — two selectors is a 422, and so is any unknown field (a typo must fail loudly, never silently widen the run to the whole state).
Finding a record's GLID: call POST /api/v1/leads/browse with {"filters":[{"field":"lead_ref","op":"eq","value":"GL-CO-00042"}]} to verify a GLID resolves to a real entity. The full filter field list lives at GET /api/v1/schema/attributes.
Stages: pass stages="all" (default), a single stage name, the shortcut "enrich" (= skip_trace + gapfill + validate), or a comma-separated list. Canonical stage order at GET /api/v1/pipeline/stages.
Returns 202 with a job_id. Poll GET /api/v1/pipeline/jobs/{job_id} for status.
Request
- Base URL: https://app.goodleads.club (the document declares no server; this is the origin it was published from)
- URL: https://app.goodleads.club/api/v1/pipeline/trigger
- Auth: API key in header X-API-Key
Request body
Example request
{
"summary": "Run scoring on a single record by GLID",
"value": {
"entity_id": "GL-CO-00042",
"stages": "score",
"state": "CO"
}
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.