Internal Secret Incidents
Request a new presence check for a secret incident
Changed onRequest a new presence check for a secret incident, to find out whether its occurrences are still present on their sources.
The check runs asynchronously: a 202 means it was enqueued, not that it completed. Read the incident back to get the refreshed presence of its occurrences.
Occurrences checked less than a minute ago are skipped, so a 202 does not guarantee that a new check was enqueued for every occurrence.
post/v1/incidents/secrets/{incident_id}/check-presence
Request
- Base URL: https://api.gitguardian.com
- URL: https://api.gitguardian.com/v1/incidents/secrets/{incident_id}/check-presence
- Auth: HTTP bearer
Path parameters
incident_idinteger required
The id of the incident to retrieve
Response
The presence check was enqueued.
Example response
{
"detail": "Presence check enqueued."
}Changes
- breaking
removed the success response with the status
- info
added the success response with the status
- breaking
- info
endpoint added
- info