![]()
api.gitguardian.com · Developer toolsSubscribeShare
GitGuardian API breaking changes
The breaking changes GitGuardian API announced that Okapi tracks: 6 in all.
Do you run the GitGuardian API? Make sure your users call it right →
At a glance
- API host
api.gitguardian.com- Kind
- Developer tools
- Versions with breaking changes
- v1 (6)
- Breaking changes tracked
- 6 breaking changes with no date yet
- Last updated
Deprecated, no date yet 6
-
No date
GET /v1/incidents/secrets/{id}/invitationsEndpoint removal Deprecated, no date -
No date
GET /v1/incidents/secrets/{id}/membersEndpoint removal Deprecated, no date -
No date
GET /v1/incidents/secrets/{id}/teamsEndpoint removal Deprecated, no date -
No date
GET /v1/teams/{id}/incidents/secretsEndpoint removal Deprecated, no date -
No date
POST /v1/incidents/secrets/{id}/grant_accessEndpoint removal Deprecated, no date -
No date
POST /v1/incidents/secrets/{id}/revoke_accessEndpoint removal Deprecated, no date
Where Okapi reads it
- Changelog api.gitguardian.com/docs
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub