List where a secret was found

List every place a secret was found: file, line, commit and whether a push or the history scan found it.

GET/repos/{owner}/{name}/secret-scanning/alerts/{id}/locations

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: security with action secret_locations, and the same inputs
Scope: An access token needs security:read.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.
`id`	string	Yes	The alert’s id: sec_…

Example request

curl https://api.g1t.sh/repos/flagon-io/hello/secret-scanning/alerts/sec_01kq2m7d4e5f6g7h8j9k0m1n2p/locations \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "path": "scripts/release.sh",
    "line": 12,
    "commit": "4807077b296e6edbf410d55e72749d3e1170c291",
    "source": "push",
    "found_at": "2026-10-06T09:14:02.118Z"
  }
]

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
422	`invalid`	The input is not valid. `message` says which field and why.