GitHub API

GitHub user profiles, repository search with stargazers, and developer public activity feed.

4 endpoints · 1 credit = $0.001. Each endpoint has its own credit cost, listed below. Calls that fail because of a service error are refunded.

Get 1,000 free credits View endpoints

GitHub Scraper

Free Trial: 50 of 50 left

GitHub

Quick presets:

Ready to Extract Live Data

Select an API above, enter your target, and click "Extract Data" to inspect real-time structured data.

LINKEDIN Result

Live 200 OK

Ready ?

No request yet. Run a test to see the actual response.

What you can build with the GitHub API

The GitHub API on AxioAPI reads public GitHub data as JSON: user profiles, repository search, details of a repository and a user's public activity. Use it as a GitHub scraper API for developer research, recruiting tools and open-source dashboards.

Research a developer

Fetch a profile and public activity to see what a developer works on.

GET /api/v1/social/github/users/{username}

Find repositories

Search repositories by query and read stars, language and links from the results.

GET /api/v1/social/github/repos

Monitor a repository

Read repository details on a schedule to track stars and metadata over time.

GET /api/v1/social/github/repos/{owner}/{repo}

Guides: GitHub scraper API: search repos and profiles in Python

How the GitHub API works

1
Choose the operation

User and activity take a username; repository search takes a query; repository details take an owner and a repo name.
2
Call the endpoint

For example GET /api/v1/social/github/repos with a query.
3
Handle event types

Activity items have different event types. Read the returned fields instead of treating every event the same.

Try the GitHub Scraper API with your own account

New accounts receive 1,000 credits after verification, enough for about 2000 calls to "GitHub User Profile".

Get 1,000 free credits Read the docs

Using GitHub Scraper

Choose a user profile, repository search or user activity.

Repository search uses a query rather than the profile username field. Keep pagination parameters consistent.

Activity items can have different event types. Read the returned fields instead of treating all events as posts.

GitHub API endpoints and pricing

OpenAPI 3.1 JSON

Select an operation above and open API & Docs for parameters and cURL, JavaScript, Python or PHP examples. The web tool uses your signed-in session; external integrations use a Bearer API key.

Method	Endpoint	Cost
GET	GitHub User Profile `/api/v1/social/github/users/{username}` Try it Helpful?	0.5 credit / request≈ $0.0005
GET	GitHub Repository Search `/api/v1/social/github/repos` Try it Helpful?	0.5 credit / request≈ $0.0005
GET	GitHub Public Activity Feed `/api/v1/social/github/users/{username}/activity` Try it Helpful?	0.5 credit / request≈ $0.0005
GET	GitHub Repository Detail `/api/v1/social/github/repos/{owner}/{repo}` Try it Helpful?	0.5 credit / request≈ $0.0005

GitHub API: frequently asked questions

What does the GitHub API return?

Public GitHub data: a GitHub user profile, GitHub repository search and repository details, and GitHub activity.

Is this a GitHub scraper API?

Yes. It returns public GitHub profiles, repositories and activity as clean JSON, so you do not need to scrape github.com or manage tokens and rate limits yourself.

Do I need a GitHub token?

No. You call AxioAPI with your API key.

Does it return private repositories?

No. Only public data.

Why does repository search not use the username field?

Repository search takes a query, which is separate from a profile username. Keep pagination parameters consistent.

How is this different from the official GitHub REST API?

The official GitHub REST API limits unauthenticated requests to 60 per hour and authenticated ones to 5,000 per hour per token, and you manage the tokens. Here you call AxioAPI with a single key and pay per request, so you do not manage GitHub tokens or their hourly limits yourself.

How is it billed?

Per request, as shown in the endpoint table below. New accounts receive 1,000 credits after verification.

Before integrating

Live and example data

Check the Live or Sandbox label before running. Examples demonstrate the response structure and do not guarantee live service status.

Credits and limits

Pricing depends on the endpoint and billable units. Failed live requests are not replaced with billable examples. Check your account limits before running repeated requests.

View pricing

Handling errors

Keep the request ID for troubleshooting. For 429, respect Retry-After when provided. If a create or delete request loses its connection, check the resource state before retrying.

Related APIs

All APIs

Often used together: LinkedIn Scraper API · Bluesky API, Telegram API & More · DNS Lookup API, BIN Lookup & Tech Stack

Ready to integrate the GitHub Scraper API? Create an account and get your API key in minutes.

Get 1,000 free credits View pricing