---
title: "Refresh Lead Finder"
method: POST
path: "/api/experiments/{key}/lead-finder/refresh"
tags: ["Experiments"]
---

# Refresh Lead Finder

`POST /api/experiments/{key}/lead-finder/refresh`

Recompute the lead-finder read model now, instead of waiting for the tick.

Accepted, then done in the background — the work is cohort-sized and an
HTTP request is the wrong place for it. Measured 27.08: a full pass over
the 197k-lead probe outlived the gunicorn worker's max-requests recycle
and came back as a 500 after 83 seconds, having done the work and thrown
it away. The cron pass has no such ceiling; only this escape hatch did.

Poll ``GET …/lead-finder`` for the result: ``computed_at`` is the oldest
stamp among the segments, so it moves when the pass has actually landed.

## Path parameters

- `key` string, required

## Headers

- `x-admin-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/explee/apis/explee-api.md) · [All operations](https://skmtc.dev/explee/apis/explee-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/explee/explee-api/revisions/f169bc6e9447/schema)
