# GitHub Search Repos API (https://www.socialcrawl.dev/platforms/github/search-repos) > Searches public repositories across GitHub via the `/search/repositories` endpoint, with GitHub's own qualifier syntax: `topic:web-scraping`, `language:python`, `stars:>1000`, `pushed:>2026-01-01`, `org:vercel`, `fork:false`, `archived:false`. Each item under `data.items[]` is one repository: `post.url`, the description in `post.content.text`, the owner in `post.author`, and `post.ext.name`, `full_name`, `stars`, `forks`, `open_issues`, `pushed_at` and `programming_language`, the same leaves `/v1/github/profile/repos` returns. `data.total` carries GitHub's total match count. Sort by `stars`, `forks`, `help-wanted-issues` or `updated`; relevance by default. Shares GitHub's search rate limit with `/v1/github/search`. TL;DR: `GET /v1/github/search/repos` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup. ## Parameters | Parameter | Required | Description | | --- | --- | --- | | `query` | yes | GitHub repository search query (GitHub's qualifier syntax: see https://docs.github.com/en/search-github/searching-on-github/searching-for-repositories). | | `sort` | no | Sort field: `stars`, `forks`, `help-wanted-issues`, `updated`. Defaults to best-match relevance. (stars \| forks \| help-wanted-issues \| updated) | | `order` | no | `asc` or `desc`. Defaults to `desc`. Needs `sort`. (asc \| desc) | | `per_page` | no | Results per page (1-100). Defaults to 30. | | `page` | no | 1-indexed page number. | | `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. | | `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. | | `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. | | `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. | | `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. | ## Code example ```bash curl -G "https://www.socialcrawl.dev/v1/github/search/repos" \ --data-urlencode "query=topic:web-scraping" \ -H "x-api-key: sc_YOUR_API_KEY" ``` ## FAQ ### What does the GitHub Search Repos API return? Returns GitHub repositories that match a query, each with name, owner, description, main language, star, fork and open issue counts and last push, plus the total match count. The response uses the same JSON envelope as every SocialCrawl endpoint, with the data, credits_used and request_id fields. ### When should I use the GitHub Search Repos endpoint? Use it to find repositories on a topic or in a language across GitHub. For issues and pull requests, use the search endpoint. ### How much does the GitHub Search Repos API cost? Each call costs 1 credit, so the 100 free credits every new account gets cover 100 calls. Credits for failed or empty calls are refunded automatically, and there is no subscription. ### What parameters does the GitHub Search Repos API need? The one required parameter is query (gitHub repository search query). It also accepts 9 optional parameters, all listed on this page. ### How do I call the GitHub Search Repos API? Send a GET request to https://www.socialcrawl.dev/v1/github/search/repos?query=topic%3Aweb-scraping with your API key in the x-api-key header. An Authorization: Bearer header works too. See the full GitHub API: https://www.socialcrawl.dev/platforms/github ## Pricing - Standard endpoints: 1 credit per call - Advanced endpoints: 5 credits per call - Premium endpoints: 10 credits per call - 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire. - Full pricing: https://www.socialcrawl.dev/pricing ## Explore with AI Questions this API answers, phrased for an AI assistant: - What does the SocialCrawl GitHub Search Repos API return? - How do I get GitHub Search Repos data with the SocialCrawl API?