posthog
Trigger Rescore
Changed onRe-score existing customers with the current classification weights.
This is the "Reclassify" action: it re-applies weights to customers we already have (via rescore_posthog_customers, which maps emails->person_id over HogQL and does NOT re-import persons). New-person discovery is a separate background job (posthog_sync), not this endpoint.
post/api/v1/posthog/rescore
Request
- Base URLhttps://api.minro.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.minro.com/api/v1/posthog/rescore
- Authnone declared
Headers
authorizationstring nullable
Bearer <token>
Response
Successful Response
Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- info
the
response's property default value{"request_id":"","timestamp":"2026-09-16T23:27:36.856600"}was removed for the status - info
the
response's property default value2026-09-16T23:27:36.856600was removed for the status
- info