Live Instagram profile

Reads one Instagram profile from the source right now: the counts, the business fields, and the twelve most recent posts with their like and comment counts. That last part is what makes this different from every other live read in the API - Instagram is the one platform whose profile fetch returns real per-post engagement, so the rate you get back is measured rather than estimated.

This is a live read: it goes to the platform at request time, returns cache_age_s = 0, and is metered against a separate live-per-minute bucket on top of your tier. It needs the scrape:live scope (Live scrape): Read from the platform itself rather than from the catalog: a profile or channel on any of the seven platforms, and on X the whole content layer - timelines, posts, replies, quotes, threads, followers, search, lists and communities.

curl "https://crmsolid.com/data-api/v2/scrape/instagram/user?handle=nasa" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/scrape/instagram/user?handle=nasa", {
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
  },
});

if (!res.ok) {
  const { error } = await res.json();
  throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}

const { data, meta } = await res.json();

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/scrape/instagram/user?handle=nasa",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    timeout=30,
)
res.raise_for_status()

payload = res.json()
data, meta = payload["data"], payload["meta"]

Keys look like psk_live_... for production keys, psk_test_... for test keys and are minted in the panel.

User id

528817151

Handle

nasa

Display name

NASA

Bio

Explore the universe and discover our home planet.

Followers

104,451,002

Following

78

Posts

4,318

Is verified

yes

Is business

yes

Category

Government Organization

External url

https://www.nasa.gov/

Avatar url

https://scontent.cdninstagram.com/v/t51.2885-19/...

Engagement rate

0.421

Avg likes

402,118

Avg comments

2,904

Posts analyzed

12

Recent posts

1 items

Partial

no

Source

iglookup

{
  "data": {
    "user_id": "528817151",
    "handle": "nasa",
    "display_name": "NASA",
    "bio": "Explore the universe and discover our home planet.",
    "followers": 104451002,
    "following": 78,
    "posts": 4318,
    "is_verified": true,
    "is_business": true,
    "category": "Government Organization",
    "external_url": "https://www.nasa.gov/",
    "avatar_url": "https://scontent.cdninstagram.com/v/t51.2885-19/...",
    "engagement_rate": 0.4213,
    "avg_likes": 402118,
    "avg_comments": 2904,
    "posts_analyzed": 12,
    "recent_posts": [
      {
        "shortcode": "C9xExamplE",
        "taken_at": "2026-08-29T18:02:44.000Z",
        "like_count": 511204,
        "comment_count": 3118,
        "view_count": null,
        "is_video": false
      }
    ],
    "partial": false,
    "source": "iglookup"
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "cache_age_s": 0
  }
}

• 401Unauthorizedunauthorized | invalid_key

  No key was presented, or the key is unknown, revoked or expired.

• 402PaymentRequiredpayment_required | subscription_inactive

  The key is valid but the plan behind it cannot serve the call: the included requests are spent and overage is switched off, capped or unfunded (payment_required), or the billing period lapsed and was not renewed (subscription_inactive). Retrying does not help; paying does. The X-Plan-* headers on this response say how far past the line you are.

  Carries X-Plan, X-Plan-Limit, X-Plan-Overage, X-Plan-Period-End, X-Plan-Remaining.

• 403Forbiddenforbidden_scope | forbidden_ip

  The key is valid but not allowed to make this call: it lacks the scope, or the request came from an address outside the key's allowlist.

• 422InvalidRequestinvalid_request

  A parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.

• 429RateLimitedrate_limited | quota_exceeded

  Either the burst ceiling for the current minute or the daily quota is spent. Distinguish with the code: rate_limited clears within the minute, quota_exceeded does not clear until 00:00 UTC.

  Carries Retry-After, X-Quota-Limit, X-Quota-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Request-Id.

• 500InternalErrorinternal_error

  Something failed on our side. Internals are never leaked; quote the request id.

• 503Unavailableupstream_timeout | upstream_error | not_configured

  The request could not be served right now. BRANCH ON error.code, not on the status: 'upstream_timeout' means a source was too slow (this is what a catalog query hitting its 15-second statement timeout returns, so it is reachable from any endpoint that reads the corpus, not only the live-scrape ones) and the same call is worth retrying with backoff - narrowing it with a smaller limit, a filtered scope or a less popular account makes it far less likely; 'upstream_error' means a source was unreachable, so back off further; 'not_configured' means the capability has no backing service in this deployment, and retrying will never help.

Every response carries X-Request-Id and meta.request_id. Quote it in support requests.

Live reads count against the live column as well as the ordinary one, so a burst of them runs out of the live bucket first. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

• GET/scrape/x/userLive X profile
• POST/scrape/x/usersLive X profiles, batched
• GET/scrape/telegram/channelLive Telegram channel read
• GET/scrape/statusLive backend health and capacity

Reference path: /data-api/reference/scrape-instagram-user