Get an Instagram profile and its stats
Run job:instagram.user.profile through the looot API: 2 providers, from $0.0015 per result. Inputs, prices, output shape and code for curl, JavaScript and Python.
Get an Instagram profile and its stats.
Job id instagram.user.profile, in Social data (Instagram). As of 2026-10-01, 2 providers serve it through 4 tools. Run job:instagram.user.profile and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
A job run takes shared input names; looot maps them to each provider’s own fields. See Job inputs.
| Input | Taken by |
|---|---|
handle |
2 of 3 providers |
user_id |
1 of 3 providers |
Any other key you send passes through unchanged. Each tool’s own fields are on its page below.
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| Bright Data | brightdata-instagram-profile |
$0.0015 per result |
| ScrapeCreators | scrapecreators-instagram-basic-profile |
$0.00188 per call |
| ScrapeCreators | scrapecreators-instagram-profile |
$0.00188 per call |
| ScrapeCreators | scrapecreators-instagram-profile-post-count |
$0.00188 per call |
A call that fails at the provider costs $0. See What’s free.
Output
Each provider answers in its own shape. Shape of the run’s result from scrapecreators-instagram-profile, checked against 1 real answer:
{ data: { user: { pk, zip, gating, fbid_v2, category, username, bio_links: { ... }[], biography, city_name, full_name, is_private, is_business, is_verified, account_type, address_street, follower_count, is_unpublished, linked_fb_info, has_profile_pic, is_memorialized, profile_pic_url, is_regulated_c18, supervision_info, friendship_status, has_story_archive, is_coppa_enforced, latest_reel_media, live_broadcast_id, should_show_category, mutual_followers_count, biography_with_entities: { ... }, hd_profile_pic_url_info: { ... }, show_text_post_app_badge, live_broadcast_visibility, text_post_app_ba... ...
The shape is cut here. Signed in, looot inspect scrapecreators-instagram-profile prints all of it.
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:instagram.user.profile","input":{"input":[]},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:instagram.user.profile",
input: {
input: [],
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:instagram.user.profile",
"input": {
"input": [],
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:instagram.user.profile.