GitGuardian API
GET /v1/incidents/secrets/{id}/invitations endpoint removal
Deprecated, no dateSubscribe to GitGuardian APIShare
GitGuardian API has deprecated GET /v1/incidents/secrets/{id}/invitations without a shutdown date. Calls made to this endpoint will eventually fail. GitGuardian API notes that this endpoint has been replaced.
Calls it hits
GET /v1/incidents/secrets/{id}/invitations
What to use instead of these calls
Call GET /v1/secret-incidents/{incident_id}/invitations instead.
In GitGuardian API's words
DEPRECATED: This endpoint has been replaced by /v1/secret-incidents/{incident_id}/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
- Verified
- , against GitGuardian API's own pages
Questions
When does this change take effect?
GitGuardian API deprecated GET /v1/incidents/secrets/{id}/invitations 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}/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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.