Generate a Snyk API token from your Snyk account settings.
Send GET to https://api.snyk.io/rest/orgs/YOUR_ORG_ID/issues with the Authorization: token YOUR_API_TOKEN header and the required version query parameter.
Add query parameters such as scan_item.type, severity, and type to filter results as needed.
Parse the data array in the response; each item represents an issue with attributes including severity, title, and affected packages.
Follow the next link in the links object to paginate through all results.
Use the issue IDs from this response to fetch individual issue details or trigger remediation workflows.
Known gotchas
The org-wide issues endpoint GET /rest/orgs/{org_id}/issues is the correct REST API path; a per-project issues endpoint exists only in the legacy v1 API and should not be used for new integrations.
The version query parameter is mandatory for Snyk REST API calls — omitting it will result in a 400 error.
Large organizations may have thousands of issues; always implement pagination using the links.next field rather than assuming all results fit in a single response.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp