Tutorial · Python
How to scrape Instagram profiles with Python (2026)
A Python walkthrough for GET /v1/instagram/profiles/{handle}. Copy the snippet, run it, then read the JSON.
GET /v1/instagram/profiles/{handle} · 1 credit per successful request.
In this tutorial
You'll pull a public Instagram profile and see the fields you get back.
Example job: refresh a creator roster from Instagram handles you already have.
Step 1
Get ready
Get a Social Fetch API key and a Python environment ready. New accounts include 100 free credits.
API key. Create a Social Fetch account and copy an API key. New accounts include 100 free credits.
Python setup. Python 3 with requests installed (pip install requests). Export SOCIALFETCH_API_KEY.
When you're done, SOCIALFETCH_API_KEY is set in your shell.
Step 2
Make the request
Copy the Python snippet, set SOCIALFETCH_API_KEY, and call GET /v1/instagram/profiles/{handle} with the x-api-key header. Example: /v1/instagram/profiles/natgeo.
You should see HTTP 200, then response.json() with data and meta. Call raise_for_status() before parsing.
Step 3
Read the response
JSON with data (the profiles) and meta (creditsCharged, requestId). Sample below is illustrative — field docs live on the endpoint page. Credits charge on completed lookups, not transport failures.
Check data.lookupStatus when present. Keep meta.requestId if a row looks wrong.
Watch out
profile card only — posts and reels are sibling endpoints. private ≠ not_found. If you store a numeric user id, the basic profile-by-userId route is lighter than re-resolving the handle.
Step 4
You finished
Same path and credits in playground, docs, and production. Pick a next step below.
FAQ
Common questions
Do I need an official Instagram developer account?
No. Social Fetch authenticates with your Social Fetch API key. You call GET /v1/instagram/profiles/{handle} and we handle upstream access. You still need to follow each platform's terms for how you use public data.
What does the instagram profiles endpoint return?
A JSON envelope with data (the profiles) and meta (creditsCharged, requestId). Shape details and field docs live on the endpoint page and in the OpenAPI docs.
Does the Instagram profile endpoint return posts or reels?
No. This route returns the profile card only. For recent posts use GET /v1/instagram/profiles/{handle}/posts; for reels use GET /v1/instagram/profiles/{handle}/reels. If you already store a numeric user id and want a lighter card, use the basic profile-by-userId route instead.
What is the difference between private and not_found on Instagram profiles?
not_found means no public profile matched that handle. private means the account is private — you may still see limited fields, but do not treat the row as a full public card. Always branch on lookupStatus before writing CRM rows.
How much does a successful request cost?
1 credit per successful request.
Is this okay for production?
Yes — same production API as everywhere else: typed errors, requestId on every response, credits charged only on completed lookups. New accounts get 100 free credits.
Any Python-specific tips for this request?
Yes. Call response.raise_for_status() before response.json(), set a timeout on requests.get, and keep response.json()["meta"]["requestId"] when a row looks wrong.
Related