Developer

Get a GitHub user or organization · GitHub API

GET/github/users/{username}
$min $0.003

Returns a public GitHub user or organization profile: name, bio, company, location, blog, follower and repository counts. Returns `not_found` when the account does not exist.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/github/users/{username} \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

usernamepathrequired
GitHub username of a user or organization.
The parameter for this GitHub operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the GitHub API in the developer category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs GitHub public data alongside Hacker News, social or web data, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Resolve a public GitHub identity into structured profile metadata for enrichment agents.
  • Refresh creator, company, or account snapshots without managing source-specific response shapes.
  • Give an AI agent a stable GitHub data source without building a per-platform integration.
  • Normalize GitHub responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields in the data object

A successful Get a GitHub user or organization call returns one data object with these fields (12 of 21 shown — the docs list the full schema).

platformstring | null
Social platform for this profile. One of: github.
usernamestring | null
GitHub username (login).
display_namestring | null
Public display name when set on the profile.
biostring | null
Profile biography text.
avatar_urlstring | null
Avatar image URL when available.
profile_urlstring | null
Canonical public GitHub profile URL.
platform_user_idstring | null
GitHub user or organization id as a string.
node_idstring | null
GitHub node id when available.
account_typestring | null
Whether this profile is a user or organization account. One of: User, Organization.
companystring | null
Company shown on the profile when available.
locationstring | null
Location shown on the profile when available.
blogstring | null
Blog or website URL from the profile when available.