Instagram Suggested Users
Get the accounts Instagram suggests as related to a public profile, from a username or profile URL.
GET · POST1 credit / successful callSingle lookup
Overview
Section titled “Overview”Send a username or profile URL in urls. You get back a related object with the source username and a list of related_profiles, each with a username, full name and verified flag.
It’s a single lookup.
Use cases
Section titled “Use cases”- Expand a creator list from one seed account.
- Map which accounts Instagram groups together in a niche.
Request
Section titled “Request”curl -G "https://api.scrapier.io/api/v2/instagram-suggested-users/" \ -H "X-API-Key: YOUR_API_KEY" \ --data-urlencode "urls=https://www.instagram.com/mrbeast/" \ --max-time 210const params = new URLSearchParams({ urls: "https://www.instagram.com/mrbeast/" });
const res = await fetch(`https://api.scrapier.io/api/v2/instagram-suggested-users/?${params}`, { headers: { "X-API-Key": "YOUR_API_KEY" }, signal: AbortSignal.timeout(210_000),});const body = await res.json();if (!res.ok) throw new Error(body.error ?? body.detail ?? `HTTP ${res.status}`);
console.log(body.data.related);import requests
resp = requests.get( "https://api.scrapier.io/api/v2/instagram-suggested-users/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"urls": "https://www.instagram.com/mrbeast/"}, timeout=210,)body = resp.json()if not resp.ok: raise RuntimeError(body.get("error") or body.get("detail"))
print(body["data"]["related"])curl -X POST "https://api.scrapier.io/api/v2/instagram-suggested-users/" \ -H "X-API-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"urls":"https://www.instagram.com/mrbeast/"}' \ --max-time 210Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
X-API-Key header | string | yes | — | Your API key from the dashboard. |
urls | string | yes | e.g. https://www.instagram.com/mrbeast/ | Instagram username or profile URL. Lookup endpoint. |
cursor | string | no | — | Pagination cursor returned in the previous response's next_cursor. Pass it back unchanged to fetch the next page. When next_cursor is null, you have reached the last page. |
Advanced
| Name | Type | Default | Description |
|---|---|---|---|
use_proxy | boolean | true | Route the request through Scrapier's residential proxy pool. Default: true. Leave as is unless support tells you otherwise. |
raw_data | boolean | false | When true, the response carries the full raw upstream payload(s) the scraper received (GraphQL / JSON API bodies, HTML, embedded JSON-LD -- exactly as the platform returned them) under raw_responses, in place of the formatted items. When false (default) you get the formatted output. Pagination (cursor / next_cursor) works the same in both modes. |
Response
Section titled “Response”{ "success": true, "data": { "urls": "instagram", "related": { "username": "instagram", "related_profiles": [ { "username": "natgeo", "full_name": "National Geographic", "is_verified": true } ] }, "next_cursor": null }}Bad input. The exact message varies by endpoint.
{ "success": false, "error": "…"}Balance below the endpoint’s price.
{ "error": "Insufficient credits. Buy more to scrape more.", "balance": 1, "required": 2}Invalid or unknown API key.
{ "detail": "Authentication service unavailable or invalid API key."}Throttled — wait for Retry-After.
{ "detail": "Request was throttled. Expected available in N seconds."}Sample from the live catalog; arrays trimmed to 3 items. Results are in data.related.
Response fields
Section titled “Response fields”| Field | Type | Example | Description |
|---|---|---|---|
urls | string | — | |
related | object | {…} | The results. |
next_cursor | null | null | Pass back as cursor for the next page. null on the last page. |
related.username | string | — | |
related.related_profiles | array | [1 item] | — |
Pagination
Section titled “Pagination”Returns everything in one call; next_cursor is always null.
Errors
Section titled “Errors”Failed calls are free. Branch on the HTTP status and read the message from error (or detail). Full details in Errors.
| Status | Meaning | Retry? | Charged? |
|---|---|---|---|
400 | Bad or missing input. | No — fix the params | No |
401 / 403 | Missing, invalid or revoked API key. | No — fix the key | No |
402 | Out of credits (body has balance). | No — top up | No |
404 | Unknown endpoint slug. | No — check the slug | No |
429 / 503 | Busy or throttled. | Yes — after Retry-After | No |
5xx | Target site or upstream failure, or timeout. | Yes — with backoff | No |
- Nothing special: send the inputs, read the result.
Related
Section titled “Related”- Instagram Profile — Look up a public Instagram account by username, @handle or URL and get its bio, follower, following and post counts and verification status.
- Instagram Profile Full — Get a public Instagram profile together with its recent posts (with like and comment counts) and related accounts in one call.
- Instagram Profile Search — Search Instagram accounts by keyword and get usernames, names, follower counts and verification status.