Instagram Followers List API

Instagram Followers List

Features

• Multi-account follower collectionSubmit one or more Instagram usernames and request follower profiles for every source account in one asynchronous task.
• Normalized follower identityReturn available profile ID, username, display name, derived profile URL, and public profile image for each follower row.
• Visibility and source signalsPreserve verification and private-account flags plus the source username and follower relationship when those values are exposed.
• Observed list contextKeep the source position and Actor scrape time when available, with SocQ collection time as the timestamp fallback.
• Per-username result controlApply results_limit separately to each submitted username, with a default of 100 and an accepted range from 1 through 2,000.

Parameters

How to Use

Submit public Instagram usernames, track the asynchronous task, and page through normalized follower profile records after collection succeeds.

1. Prepare one or more public Instagram usernames; a leading @ is accepted and removed before collection.
2. POST usernames and an optional results_limit to /v1/instagram/followers-list, then store the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
4. Read data.results.items and follow next_cursor while has_more is true.

curl -X POST "https://api.socq.ai/v1/instagram/followers-list" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"usernames":["instagram"],"results_limit":100}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Public audience sampling: Build a bounded sample of follower usernames, display names, profile links, visibility flags, and observed positions for a selected public account.
• Cross-account overlap checks: Group rows by extra.source_username and compare follower IDs or usernames to identify profiles appearing under more than one submitted account.
• Profile enrichment queues: Select returned usernames and pass them to Instagram Profiles when a workflow needs biography or visible profile-count fields.
• Relationship-list snapshots: Store follower identity, source username, observed position, and collected_at to make later public-list samples distinguishable.

Pro Tips

• When submitting several usernames, estimate requested depth as usernames multiplied by results_limit because the cap and credit estimate apply per source account.
• If a source username begins with @, you may send it unchanged; the provider mapper removes leading @ characters before the Actor run.
• When comparing accounts, retain extra.source_username because the same follower profile can appear in more than one source list and cross-source deduplication is not promised.
• If position is present, treat it as an observed list value rather than a stable rank or measure of relationship strength.
• When a public source returns fewer rows than requested, keep the partial result and record collected_at; privacy, account availability, source pagination, and Actor limits can reduce output.

Related APIs