Snyk API
v1 group audit log search removal
Stopped workingSubscribe to Snyk APIShare
On January 22, 2025, Snyk removed the POST /v1/group/{id}/audit* endpoint. Requests sent to this path fail after that date. The change affects callers relying on the v1 group audit log search functionality.
Calls it hits
POST /v1/group/{id}/audit*
What to use instead of these calls
Call the REST audit logs API GET /rest/groups/{group_id}/audit_logs/search instead. This switch requires updating your implementation to use RFC3339 formatted from and to parameters as well as cursor pagination.
In Snyk API's words
Group and org level audit logs v1 January 22, 2025 Search Audit Logs (Group and Org) v1 API to GA REST Audit logs API migration guide
Facts
- API
- Snyk API
api.snyk.io - Kind
- Removal
- Announced
- July 22, 2024
- Takes effect
- January 22, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Snyk API's own pages
Questions
When does this change take effect?
Calls to POST /v1/group/{id}/audit* on Snyk API stopped working on January 22, 2025.
What happens to calls after January 22, 2025?
They have failed since January 22, 2025.
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 Snyk API 3
-
/v1/org/{id}/projectsEndpoint removal Stopped working -
POST /v1/org/{id}/audit*Removal Stopped working -
/v1/reporting/*Removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.