Snyk API
v1 Reporting API removal
Stopped workingSubscribe to Snyk APIShare
Endpoints matching /v1/reporting/* were shut down on April 27, 2026. Requests sent to these paths fail since that date. The removal was announced on July 22, 2024.
Calls it hits
/v1/reporting/*
What to use instead of these calls
Switch to the Export API by calling POST /rest/groups/{group_id}/export or /rest/orgs/{org_id}/export to start a job, polling GET /rest/groups/{group_id}/jobs/export/{export_id}, and retrieving the CSV from GET /rest/groups/{group_id}/export/{export_id}. Because the Export API is asynchronous and returns CSV files instead of JSON, reporting workflows require a redesign around export jobs rather than a simple endpoint update.
The Export API is asynchronous and returns CSV files instead of JSON: the reporting code must be redesigned around export jobs.
In Snyk API's words
/v1/reporting v1 April 27, 2026 V1 Reporting APIs to Export API migration guide
Facts
- API
- Snyk API
api.snyk.io - Kind
- Removal
- Announced
- July 22, 2024
- Takes effect
- April 27, 2026
- 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 /v1/reporting/* on Snyk API stopped working on April 27, 2026.
What happens to calls after April 27, 2026?
They have failed since April 27, 2026.
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/group/{id}/audit*Removal Stopped working -
POST /v1/org/{id}/audit*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.