SigSentry Documentation

Returns every code repository connection attached to the current project. Credentials are never included in the response.

Authentication

API key with config:read permission. Project-scoped or tenant-scoped (with X-Project-Id).

Endpoint

GET /v1/config/repos

No path or query parameters. The current project's id is implied by the API key (or X-Project-Id for tenant-scoped keys).

Response

200 OK

{
  "success": true,
  "data": [
    {
      "id": "rc_x1y2z3...",
      "platform": "github",
      "repositories": ["acme/checkout-api", "acme/billing-worker"],
      "serviceMappings": [
        {
          "serviceName": "checkout-api",
          "repo": "acme/checkout-api",
          "pathPrefix": "src/",
          "defaultBranch": "main"
        }
      ],
      "lookbackDays": 30,
      "isActive": true,
      "createdAt": "2026-04-01T10:15:00Z",
      "updatedAt": "2026-04-12T18:22:00Z"
    }
  ]
}

Field	Type	Notes
`id`	UUID	The connection id
`platform`	`'github' \| 'gitlab' \| 'bitbucket'`	Source platform
`repositories`	`string[]`	Repos this connection covers, in `owner/repo` form (or `group/project` for GitLab, `workspace/repo-slug` for Bitbucket)
`serviceMappings`	array	Service-to-repo path mappings; see Service mappings
`lookbackDays`	int	How far back analyses search for related merges (1–365)
`isActive`	boolean	`false` if the connection is paused
`createdAt` / `updatedAt`	ISO 8601	Standard timestamps

Credentials are never returned. To rotate them, use PUT /v1/config/repos/{id}.

Error responses

Status	`error.code`	When
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:read`

Example

curl https://api.sigsentry.com/v1/config/repos \
  -H "Authorization: Bearer ss_secret_..."