List public repositories
GET/api/repos
listPublicRepos
Returns public repositories visible to anonymous callers. `?sort=updated` (the default) is most-recently-updated first; `?sort=trending` is most stars gained in the last seven days first, tie-broken by `updated`, and fills `star_count` on every row. Page size is bounded — pass `?limit=N` (1–200, default 50).
Authentication is not described for this operation in the spec — that does not mean it is public. Check tokens and scopes.
curl
curl -X GET 'https://neosource.dev/api/repos'fetch
fetch("https://neosource.dev/api/repos", {
method: "GET",
});Query parameters
limitMaximum number of repositories to return. Clamped to [1, 200]; defaults to 50 when omitted.
default
50sortOrdering. `updated` (the default when omitted) is most recently updated first; `trending` is most stars gained in the last seven days first, with `updated` as the tiebreak, and fills `star_count` on every row.
Responses
200Repository list
application/json
Standard errors
Bodies documented once for the whole API — see standard errors.
- 400Bad Request — one of: invalid_input
- 429Rate limited — retry after the interval in the `Retry-After` header
- 500Internal server error
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget
Schemas
Referenced above. Listed here rather than expanded inline, so the same definition is not repeated at every level.
MergeMethod
How a pull request's commits land on its target branch. A repo carries two settings over this enum (`migrations/20260820120000_repo_merge_methods.sql`): the set it *permits* (`RepoRecord::allowed_merge_methods`, never empty) and the one the merge path reaches for when the request names none (`RepoRecord::default_merge_method`, always a member of that set — enforced by the settings route, which is the only place both columns are visible at once). `Default` is [`MergeMethod::Merge`] to match the column default, which is itself the pre-existing behaviour of every repo: before this setting existed, a merge always minted a two-parent commit. `Rebase` is deliberately absent rather than merely unimplemented — it replays N commits, can conflict per commit, and rewrites the SHAs the stacked-PR re-parent invariant leans on (`plans/archive/pr-merge-methods-2026-08.md` §"Not doing"). Adding it later is one `ALTER TYPE merge_method ADD VALUE` plus an arm here, which is why the stored shape is an enum array and not a pair of booleans.
"merge""squash"
RepoMirrorStatus
[`RepoResponse::mirror_status`]: how current a `_mirror` repository is.
last_synced_atWhen the daily refresh last synced from the upstream (ms since the epoch); absent before the first sync.
latest_ci- one of
RepoParentInfo
Summary of a fork's parent repository.
repo_idrequired
RepoStatusOutput
Repo lifecycle state surfaced by the API. Mirrors `RepoStatus`. See ADR 0012 §2.
"creating""ready""importing""import_failed"
RepoVisibilityInput
"public""internal""private"