pipeline

Recompute Signals

Force-recompute RA Intelligence, Contact Relevance, and/or Classification on a scope.

ADR-004 Phase 3 surface. Runs inline — for targeted recomputes (typically 1–200 entities after an operator/agent change). Whole-state recomputes should go through the normal pipeline trigger with filters.

Bypasses the ADR-004 Phase 1 skip-if-current filter so entities already stamped at the current service version still get recomputed. That's the whole point — the operator has reason to distrust the current stamp and wants the service to run anew.

service="classify" exists because the classification service VERSION (classification_v1) has never been bumped by a keyword/taxonomy batch — shipping a new keyword does not, by itself, retroactively reclassify any entity that was already stamped (including ones stamped "unclassified"). This is the small-batch path to actually apply a shipped keyword/taxonomy change to the specific records it should have caught, without a whole-state pipeline run.

post/api/v1/pipeline/recompute-signals

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/recompute-signals
  • Auth: API key in header X-API-Key

Request body

servicestring required
statestring required
entity_idsstring[] required
forceboolean
dry_runboolean

Response

Successful Response

servicestring required
statestring required
ra_intelligenceobject nullable
contact_relevanceobject nullable
classifyobject nullable
dry_runboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.