List accounts an Instagram user follows · Instagram API
List accounts an Instagram user follows
curl https://api.unifapi.com/instagram/users/{username}/following \
-H "Authorization: Bearer $UNIFAPI_KEY"Path parameters
- username
- The public Instagram identifier shown in the endpoint path. Use the URL-visible slug or platform id described in the docs for this operation.
This operation is part of the Instagram API in the social platforms 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 Instagram public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.
Common agent workflows
- Resolve a public Instagram identity into structured profile metadata for enrichment agents.
- Refresh creator, company, or account snapshots without managing upstream-specific response shapes.
- Give an AI agent a stable Instagram data source without building a per-platform integration.
- Normalize Instagram responses into the same UnifAPI envelope used across the catalog.
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 `billing.records_charged` field matches the number of billable top-level records returned, subject to the one-record minimum.
- If the workspace balance cannot cover every upstream result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Billing
Every successful call costs at least one credit. List and search operations charge by billable records returned; single-object lookups charge one record when they succeed. Platform-caused failures can be refunded, and public responses include billing metadata with the credits charged and remaining workspace balance.
Errors and retries
Authentication, validation, rate-limit, not-found, and upstream 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.
More Instagram operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Browse Instagram's Explore feed
Browse Instagram's Explore feed
Get an Instagram location by id
Get an Instagram location by id
List Instagram locations geographically near a given location
List Instagram locations geographically near a given location
List posts tagged with an Instagram location
List posts tagged with an Instagram location