Get a finding in a repository.
Access control rules
- The requester must have access to the repository.
- Reviewers have access to the finding they and their team made.
- Clients, judges, triagers and admins have access to all findings.
Additional data
For bounty repositories, admins, clients, and triagers will also receive the researcher’s bounty finding stats (spam, rejected, confirmed counts and number of bounties participated).
Documentation Index
Fetch the complete documentation index at: https://docs.cantina.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
Reference to a finding, either a finding id or finding number.
Response
Finding with optional researcher stats
Finding within a respository.
Team id.
Status of a [Finding].
Note that the in_review status is only applicable within bounties.
new, in_review, disputed, rejected, spam, duplicate, confirmed, acknowledged, fixed, withdrawn Severity of a [Finding].
critical, high, medium, low, informational, gas_optimization User data in the context of a repository.
Whether this finding has comments unread by the current user.
The number of comments this finding has that are unread by the current user.
Only returned by list_all_findings.
Only returned by list_all_findings.
The root finding this finding is a duplicate of.
All findings that are a duplicate of this finding.
For findings that have no duplicates, this will be empty.
Only returned for admins, judges and triagers.
Likelihood of a [Finding].
high, medium, low Impact of a [Finding].
high, medium, low Only returned for admins, judges and triagers.
high, medium, low Only returned for admins.
User assigned to the finding.
Group of [Asset]s.
Timestamp of the most recent comment on this finding, if any.
Note field for additional finding information.
Payment ID linked to this finding, if any.
Status of the payment linked to this finding, if any.
planned, scheduled, submitted, disputed, executed, rejected, failed, cancelled