POST /api/dev/reset-repo
Summary
Clears all jobs associated with a given repository so the next pipeline run is treated as a first run.
Intent
This developer utility endpoint exists to reset the job state for a specific repository, useful during development, testing, or when a repository needs to be fully re-processed from scratch without any cached state.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| repoId | string | Yes | The unique identifier of the repository whose jobs should be cleared. |
Request example
curl -X POST https://maps.google.com/api/dev/reset-repo \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"repoId": "repo-123"}'Response example
{ "ok": true, "repoId": "repo-123", "message": "Jobs cleared — next run will be treated as first run"}Error cases
400— repoId is missing or not provided in the request body
Gotchas
- This is a dev-only endpoint — it is intended for development and testing purposes and should not be called in production workflows.
- Clearing jobs is irreversible; all cached job state for the repository will be permanently deleted and cannot be recovered.
- After calling this endpoint, the next pipeline run for the specified repository will behave as if it has never been processed before, potentially triggering full re-enrichment and re-processing of all endpoints.
- The repoId must exactly match the identifier used internally by the job store — passing an incorrect or mismatched repoId will silently succeed (200) but clear nothing meaningful.