FetchPI
Log in

Instagram profile API

Instagram profile data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

  • 1 documented endpoints
  • GET /v1/ig/users/{username}

Contract summary (English): Get a normalized Instagram profile (capability ig.profile)

Normalized response entity
instagram/profile
capability
ig.profile

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

  • Enrich CRM and outreach tooling with up-to-date {{platform}} profile data — follower counts, verification status and bios as structured JSON.
  • Screen creator and partner accounts before a campaign with consistent, queryable profile metrics.
  • Re-query the same handle and diff the normalized fields to track profile changes over time.

Response fields

Instagram Profile (normalized)

Normalized Instagram profile. This is the ONLY upper-layer format; provider-private fields MUST NOT appear — the Normalizer drops them. The capability id is ig.profile (the /v1/ig surface); the entity platform key is the full enum value instagram (dev-decisions §3.8 ig→instagram mapping).

FieldTypeRequiredDescription
idstringRequiredPlatform-stable user id (numeric string pk on Instagram).
platform"instagram"Required—
type"profile"Required—
usernamestringRequiredInstagram username without leading @.
display_namestring | nullOptionalThe Instagram full_name.
descriptionstring | nullOptionalThe biography.
urlstring | nullOptionalThe external_url.
profile_image_urlstring | nullOptional—
verifiedbooleanRequired—
is_privatebooleanRequiredPlatform extension field.
created_atstring | nullOptionalInstagram does not expose account creation time; normally null.
metrics.followersintegerRequired—
metrics.followingintegerRequired—
metrics.postsintegerRequiredMedia count.
fetched_atstringRequiredWhen the platform data was actually collected (UTC RFC3339).

Field notes are shown in the contract's original English.

Response meta

FieldTypeRequiredDescription
modecache | default | liveRequiredEffective mode after merging param > max_age > source policy (D-004).
age_secondsinteger | nullOptionalAge of served data; null when unknown.
source_layercache | db | upstreamRequiredWhich layer served the response (PRD §10).
stalebooleanOptionalTrue when stale data was served under stale_if_error / SWR (D-004).
billing.amount_creditsintegerRequiredMicro-USD (1e-6 USD) actually charged for this request.
billing.cache_hitbooleanRequired—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/ig/users/{username}
curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/ig/users/newdev"
{
  "data": {
    "id": "1295448945",
    "platform": "instagram",
    "type": "profile",
    "username": "creatordev",
    "display_name": "Creator Dev",
    "description": "Photo dumps and API graphs.",
    "url": "https://fetchpi.com",
    "profile_image_url": "https://cdn.example.com/profile_pic/creatordev.jpg",
    "verified": true,
    "is_private": false,
    "created_at": null,
    "metrics": {
      "followers": 51230,
      "following": 310,
      "posts": 862
    },
    "fetched_at": "2026-09-18T09:00:00Z"
  },
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 120,
      "source_layer": "db",
      "stale": false
    },
    "billing": {
      "amount_credits": 100,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

What does the Instagram profile API return?

A normalized profile object — identity, bio and audience fields as defined in the field table below — plus freshness and billing metadata.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the profile capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.