# POST /v1/incidents/secrets/{}/revoke_access is deprecated

GitGuardian API deprecated POST /v1/incidents/secrets/{id}/revoke_access without giving a shutdown date yet.

GitGuardian has deprecated the POST /v1/incidents/secrets/{id}/revoke_access endpoint without announcing a shutdown date. This call was previously used to revoke access of a user, invitee, or team to a secret incident. Calls to this endpoint will fail once it is shut down.

## What to use instead

Revoke access using DELETE /v1/members/{member_id}/{resource_type}/{resource_id}, DELETE /v1/teams/{team_id}/{resource_type}/{resource_id}, or DELETE /v1/invitations/{invitation_id}/{resource_type}/{resource_id}, passing the incident as the resource.

- API: GitGuardian API (api.gitguardian.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `POST /v1/incidents/secrets/{id}/revoke_access`
- Source: [Announcement](https://api.gitguardian.com/docs)
- Verified: November 6, 2026, against GitGuardian API's own pages
- Page: https://www.okapi.bot/providers/gitguardian-api/breaking-changes/post-v1-incidents-secrets-revoke-access-is-deprecated/

## GitGuardian API's words

> Revoke access of a user, an existing invitee or a team to a secret incident. DEPRECATED: This endpoint has been replaced by this one for members, this one for teams, and this one for invitations.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent