GitGuardian API
GET /v1/teams/{id}/incidents/secrets endpoint removal
Deprecated, no dateSubscribe to GitGuardian APIShare
GitGuardian API deprecated the GET /v1/teams/{id}/incidents/secrets endpoint without a shutdown date. This change affects calls to list secret incidents for a team, which do not return occurrences in this route. Following its eventual removal, requests to this endpoint will fail.
Calls it hits
GET /v1/teams/{id}/incidents/secrets
What to use instead of these calls
Call GET /v1/teams/{team_id}/secret-incidents instead.
In GitGuardian API's words
List secret incidents of a particular team. Occurrences are not returned in this route. DEPRECATED: THis endpoint has been replaced by /v1/teams/{team_id}/secret-incidents
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
- Verified
- , against GitGuardian API's own pages
Questions
When does this change take effect?
GitGuardian API deprecated GET /v1/teams/{id}/incidents/secrets without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: GitGuardian API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from GitGuardian API 5
-
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
POST /v1/incidents/secrets/{id}/grant_accessEndpoint removal Deprecated, no date -
No date
POST /v1/incidents/secrets/{id}/revoke_accessEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.