Repos this connection's credential can reach, for the bind pick-list (ADR-0060)
GET
/v1/connections/{id}/available-repos
const url = 'https://example.com/v1/connections/example/available-repos';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/v1/connections/example/available-reposThe forge is the authority on what a connection covers, so this is a live call, not a cached view. An adapter that cannot enumerate answers 501 rather than an empty list: “I cannot look” and “there is nothing there” must not read the same, or an admin concludes their token is scoped wrong.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”id
required
string
Connection id
Responses
Section titled “Responses”Media typeapplication/json
Array<object>
GET /v1/connections/{id}/available-repos: what the connection’s credential
reaches, and which of those Scarab already governs.
object
bound
required
Already a Project on this connection — the bind form renders it as done rather than offering a no-op that silently re-homes a live binding.
boolean
name
required
string
owner
required
string
Examplegenerated
[ { "bound": true, "name": "example", "owner": "example" }]Requires Administer on the org
No such connection, or no registry/forge wired
This forge adapter cannot enumerate repos