GitGuardian API · Endpoint removal
POST /v1/incidents/secrets/{}/revoke_access is deprecated
Deprecated, no date
GitGuardian API deprecated POST /v1/incidents/secrets/{}/revoke_access without giving a shutdown date yet.
What to use instead of these calls
Revoke access with 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}, the incident as the resource.
Calls it hits
POST /v1/incidents/secrets/{}/revoke_access
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.
Facts
- API
- GitGuardian API
api.gitguardian.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
More from GitGuardian API
- GET /v1/incidents/secrets/{}/invitations is deprecated Deprecated, no date
- GET /v1/incidents/secrets/{}/members is deprecated Deprecated, no date
- GET /v1/incidents/secrets/{}/teams is deprecated Deprecated, no date
- GET /v1/teams/{}/incidents/secrets is deprecated Deprecated, no date
- POST /v1/incidents/secrets/{}/grant_access is deprecated Deprecated, no date