2 units. A failed run costs 0. The same input within 5 min costs 0.

github-issues

Q: How do I get GitHub data through an API?

Call POST /recipes/github-issues with your key and repo and state and labels. You get rows with the 11 fields above. The recipe is tested against the live site every 6 hours.

Q: Can I try it without paying?

Yes. Sign up with Google, GitHub or email for a free key with 1,000 credits every month. No credit card.

Q: What if the site changes?

The health check runs every 6 hours against the live site. A failing recipe shows as failing on this page until we fix it.

The issues of one GitHub repository, one row per issue: number, title, url, state, author, labels, comment count, created and updated times, the first 300 characters of the body. repo is owner/name or the repository URL; state open, closed or all; labels a comma list every issue must carry; sort created, updated or comments, newest or most first. GitHub's list holds pull requests too: pull_requests true keeps them, false drops them, so a page can give fewer rows than limit. GitHub rate-limits unauthenticated calls: a refused call gives no rows and one warning line.

stagedapi.github.comWASM module11 fields2 unitsfresh 5 min

Run it below API reference

‹ Recipes

…json

POST api.crawl4ai.com/recipes/…

$ crawl recipe

Live · your key · counts against your quota✓ 200 OK

# Hit Run - the rows render here as a table, with the cost

Fields

11 columns on every row. null means the site does not state it.

field	type	meaning
number	integer
title	string
url	string
state	string
author	string
labels	string
comments	integer
created	string
updated	string
is_pull_request	boolean
body	string

null means the site does not state it.

numberinteger

titlestring

urlstring

statestring

authorstring

labelsstring

commentsinteger

createdstring

updatedstring

is_pull_requestboolean

bodystring

How it behaves

Cost. 2 units. A failed run costs 0.

Freshness 5 min. The same input within 5 min is served from cache at 0 units.

Questions about this recipeQuestions

Short answers. The API reference has the long ones.

How do I get GitHub data through an API?

Call POST /recipes/github-issues with your key and repo and state and labels. You get rows with the 11 fields above. The recipe is tested against the live site every 6 hours.

What does it cost?

Can I try it without paying?

What if the site changes?

Need more from GitHub?

Extra fields, higher volume, or a private copy with a freshness SLA. We build it on Enterprise.

Request a change

More for developers and open source

All 7 recipes →

github-repoGitHub

verified

One GitHub repository's facts, then its latest releases: the first row is the repository (stars, forks, open issues, language, license…

Startup and investor intel17 fields

3 units · fresh 10 minTry it →

github-trendingGitHub

verified

The repositories trending on GitHub today: name, description, language, stars and stars gained today.

Startup and investor intel7 fields

2 units · fresh 30 minTry it →

package-infonpm and PyPI

verified

One row of facts about a package from its registry's public JSON: latest version and when it was published, description, license, homepage…

Developers and open source11 fields

2 units · fresh 1 hTry it →

For developers

Get a free API key and run your first crawl.

1,000 credits every month. No credit card. Your self-hosted setup keeps working.

Get a free API key

For teams

Talk to us about volume, regions and an SLA.

A 30-minute call with the team that writes the crawler. DPA on request, invoice billing, your choice of US, EU or Singapore.

Book a call hello@crawl4ai.com