Instagram profile endpoint docs

Instagram About Account by User ID API docs

Use this endpoint when you already know an Instagram user ID and need the public about-account layer before opening heavier profile, content, or social workflows.

It is a practical entry point for teams that resolve creator identity, enrich account records, review public profile context, or validate whether a known Instagram account should enter a larger monitoring pipeline.

Method GET
Entity Profile
Versions 2
What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

This documentation explains what the API method is for, how V1 and V2 differ, which request parameters you need, and what the response structure looks like when a live verification example is available.

When to use it

It is a practical entry point for teams that resolve creator identity, enrich account records, review public profile context, or validate whether a known Instagram account should enter a larger monitoring pipeline.

Common use cases

Account enrichment

Attach public about-account context to known Instagram user IDs before you expand into posts, comments, or social graph collection.

Creator operations

Validate the public account layer for creator onboarding, shortlist reviews, and internal QA flows that already store Instagram user IDs.

Trust and review workflows

Inspect the method behavior and response shape before you connect the endpoint to moderation, brand-safety, or compliance-oriented checks.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters
Parameter Required Type Example Description
user_id Yes str value Numeric user ID on the selected platform.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/instagram.com/profile/about-account-by-user-id

Normalized format

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/instagram.com/profile/about-account-by-user-id" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'user_id=value'
Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Placeholder

A live verification example is not available for V2 yet. This placeholder keeps the standard response envelope visible until a verified example is ready.

{
  "success": true,
  "status": "ok",
  "data": {}
}
What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the Instagram platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs
FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

When should I use this API method instead of a broader Instagram profile endpoint?

Use it when you already have a numeric Instagram user ID and want the public about-account layer first. Broader profile API methods are a better fit when you still need identity resolution or adjacent account surfaces.

Should new integrations start with V1 or V2 on this documentation page?

Default to V2 for new product integrations because it keeps the normalized response structure stable. Keep V1 only for compatibility with existing clients that still depend on the original platform-shaped payload.

Does this page always show a verified response example?

The response section always tries to load a verified JSON example. If no verified example exists for a version yet, the page shows a standard placeholder envelope so the response structure stays visible.