Run one scoped pipeline job per state for a selection that spans states
Fan a cross-state selection out into one ordinary scoped run per state.
Each leg goes through the same POST /trigger code path it would have taken if you had picked that state by hand — same validation, same Run Manifest, same per-entity COGS attribution, same concurrency lock.
Partial success is the normal outcome, not an error. A state whose lock is held by the overnight harvest cannot start a second run, and silently dropping it is how an operator comes to believe they enriched records they did not. Every leg is reported with its own status and job_id; the call fails (409 / 400) only when nothing started.
Scope with entity_id (IDs may span states — they are grouped) or filters (no state clause; each leg adds its own). limit is per state; pull is refused because it ignores record scope.
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-multi
- Auth: API key in header X-API-Key
Request body
Example request
{
"summary": "Enrich an all-states Browse selection",
"value": {
"filters": [
{
"field": "has_email",
"op": "eq",
"value": false
}
],
"stages": [
"skip_trace",
"gapfill",
"validate"
]
}
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.