Instagram Search Profiles API
Returns public profiles matching a keyword, each with id, username, display name, verified badge, avatar and profile URL; bio and counts are null on a search row.
GET /v1/instagram/search/profilesLast updated November 2026Maintained by the SocialCrawl team
When to use the Instagram Search Profiles API
Use it to find accounts by topic through Instagram's own account search, then call instagram/profile for the bio and follower counts of the ones you keep.
Not for posts or reels (instagram/search/hashtag, instagram/search/reels), or for accounts, hashtags and places in one payload (instagram/search).
From the API reference
Searches Instagram's own account search for a keyword or phrase and returns matching public profiles mapped to the unified Author schema: id, username, display_name, verified, avatar_url, and the profile url, 20 a page with a cursor for the next. A search row carries no bio, followers, following or posts_count (they are null): fetch /v1/instagram/profile for an account you keep. The plain call has no account country: Instagram does not put that on a search stub. Send include=about to join each row to the About-this-account panel for author.ext.country, the join month, and the public email and phone the account publishes, 2 extra credits a row filled, default the top 8 (17 credits held), limit=12 for the page. A row the panel could not fill is refunded. This is not a country filter: a query that surfaces no Korean accounts still returns no Korean accounts after the join. For place-tagged posts, use /v1/instagram/search/location then /v1/instagram/location/posts.
Searching 69 platforms in parallel
What can you do with the Search Profiles API?
The Search Profiles endpoint gives you structured Instagram data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
# GET /v1/instagram/search/profiles: Metered: holds 1 credit per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 34: this endpoint's measured p99 latency x 1.5.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
# Next page: send pagination.next_cursor back as cursor until pagination.has_more is false.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 34 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/instagram/search/profiles?query=yoga" && cat response.json# GET /v1/instagram/search/profiles: Metered: holds 1 credit per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 34 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/instagram/search/profiles"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"query": "yoga",
}
# Walk the list: send pagination.next_cursor back as cursor until has_more is false.
MAX_PAGES = 10 # each page is one call
items = []
for _ in range(MAX_PAGES):
body = socialcrawl(params)
if body is None:
break
items.extend(body["data"]["items"])
page = body.get("pagination") or {}
if not page.get("has_more") or not page.get("next_cursor"):
break
params["cursor"] = page["next_cursor"]
print(f"{len(items)} items")// GET /v1/instagram/search/profiles: Metered: holds 1 credit per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 34_000; // this endpoint's measured p99 latency x 1.5.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/instagram/search/profiles");
url.searchParams.set("query", "yoga");
// Walk the list: send pagination.next_cursor back as cursor until has_more is false.
const MAX_PAGES = 10; // each page is one call
const items: unknown[] = [];
for (let page = 0; page < MAX_PAGES; page++) {
const body = await socialcrawl(url);
if (!body) break;
items.push(...body.data.items);
const next = body.pagination?.next_cursor;
if (!body.pagination?.has_more || !next) break;
url.searchParams.set("cursor", next);
}
console.log(`${items.length} items`);Parameters
| Parameter | Required | Description |
|---|---|---|
| query | Yes | Keyword or phrase matched against account usernames and display names, as Instagram's own account search does. |
| cursor | No | Pagination cursor. Pass the `next_cursor` from the previous response to get the next page; treat it as an opaque token. |
| include | No | Send `about` to fill `author.ext.country`, join month and public contact from the About panel, 2 extra credits a row filled, never more than 12 rows. A typo is a free 400. (about) |
| limit | No | Cap the rows served, and with `include=about` the credits held. 1 to 12. Default 8 when the token is present so the hold is 17, not 25. |
| max_pages | No | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| max_items | No | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| max_credits | No | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |
What does the Instagram Search Profiles API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "instagram",
"endpoint": "/v1/instagram/search/profiles",
"data": {
"items": [
{
"author": {
"id": "user_e31ddb",
"username": "user_ca3142",
"display_name": "user_b49d7e",
"avatar_url": "https://example.com/avatars/user_fb1999.png",
"bio": null,
"verified": true,
"followers": null,
"following": null,
"posts_count": null,
"likes_count": null,
"url": "https://example.com/user_ebaf89",
"external_url": null
}
},
{
"author": {
"id": "user_e7c827",
"username": "user_809007",
"display_name": "user_93c195",
"avatar_url": "https://example.com/avatars/user_e7991c.png",
"bio": "Sample comment text (redacted). Sample comment text (redacted). Sample comment text (redacted). Sample comment text (redacted).",
"verified": true,
"followers": 55321,
"following": 1728,
"posts_count": 12,
"likes_count": null,
"url": "https://example.com/user_e4917a",
"external_url": "https://example.com/user_c684fa"
}
}
],
"total": null,
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": null,
"has_more": false,
"page_size": 2
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T07:28:50.770Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Instagram Search Profiles API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 69 platforms covering 10B+ monthly active users.
One schema, every platform
Query 69 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I search for Instagram profiles by keyword via API?
Is this a native Instagram profile search?
What fields come back for each profile?
How do I paginate profile search results?
How much does profile search cost?
Ask AI about SocialCrawl
Ready to scrape Instagram Search Profiles data?
Get your API key and start pulling Instagram data in under 60 seconds.
