DELETE /v1/config/repos/{id}/cache

Forces the next analysis on this repo connection to re-fetch from the source platform instead of reusing recent data. Use as an escape hatch in these scenarios:

After a force-push that rewrote history on the default branch
After rotating credentials with PUT, to guarantee the next read uses the new token
After a large refactor if you've noticed analyses citing out-of-date file contents

You normally don't need to call this — repo data refreshes automatically over time.

Authentication

API key with config:write permission.

Endpoint

DELETE /v1/config/repos/{id}/cache

Path parameters

Param	Type	Notes
`id`	UUID	The connection id

Response

200 OK

{
  "success": true,
  "data": {
    "flushed": true
  }
}

Field	Notes
`flushed`	`true` once the request completes

Error responses

Status	`error.code`	When
400	`VALIDATION_ERROR`	`id` is not a UUID
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:write`
404	`NOT_FOUND`	No connection with that id in your tenant

Example

curl -X DELETE https://api.sigsentry.com/v1/config/repos/rc_x1y2z3/cache \
  -H "Authorization: Bearer ss_secret_..."

Idempotency

Calling this endpoint repeatedly is safe. No Idempotency-Key is required.

DELETE /v1/config/repos/{id}/cache

On this page