Skip to content

Conversation

@gitphill
Copy link

Snyk requires auth schema of "token" rather than the default "Bearer". See https://docs.snyk.io/snyk-api/authentication-for-api

It is possible to connect using a Bearer token via Snyk Apps but for the average user it's much easier to authenticate using a personal API token, as decribed in the provider readme doc/providers/snyk.md.

Moving to the latest Snyk API version 2024-10-15. The endpoints used by bomber haven't changed spec. The request and response schemas for /self and /issues remain the same.

Snyk requires auth schema of "token" rather than the default "Bearer".
See https://docs.snyk.io/snyk-api/authentication-for-api

It is possible to connect using a Bearer token via Snyk Apps but for the
average user it's much easier to authenticate using a personal API
token, as decribed in the provider readme doc/providers/snyk.md.

Moving to the latest Snyk API version `2024-10-15`. The endpoints used
by bomber haven't changed spec. The request and response schemas for
`/self` and `/issues` remain the same.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants