Developer

List accounts a GitHub user follows · GitHub API

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

Returns the accounts a GitHub user follows. Paginate with `cursor`.

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

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

Parameters

usernamepathrequired
GitHub username of a user or organization.
cursorquery
Opaque pagination cursor from a previous response's `pagination.next_cursor`. Omit for the first page.
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

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

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 on each record in data

A successful List accounts a GitHub user follows call returns data as an array; each record carries these fields.

platform_user_idstring | null
GitHub user id as a string.
node_idstring | null
GitHub node id when available.
usernamestring | null
GitHub login (username).
avatar_urlstring | null
Avatar image URL when available.
profile_urlstring | null
Canonical public GitHub profile URL.
account_typestring | null
Whether this account is a user or organization. One of: User, Organization.
is_site_adminboolean | null
Whether the account is a GitHub site administrator.
Related endpoints

More GitHub operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.