Which post format actually works on this account: GET /insights/instagram/{handle}/content-mix

What this endpoint answers

Splits an account's sampled posts by format - reel, carousel, image - and reports what each one earns against that account's own average. Reels and carousels behave differently on every account, and the only honest way to say which is working is to compare an account with itself rather than with a benchmark.

This is a catalog read: it is served from the CRM Solid database in milliseconds, costs one budget unit, and reports how old the reading is in meta.cache_age_s. It needs the insights:read scope (Insights): Engagement rates, top posts, viral patterns, cohort benchmarks.

Good to know

followers is null for any account whose follower count the crawl has not captured, which is about two thirds of the Instagram catalog. Null means unknown; it never means an account with no followers. Use GET /accounts/instagram/{handle} when you need the count itself.
vs_account_avg_pct compares a format against the account's own weighted average interactions, so +25 means that format earns a quarter more than this account typically does. It is null for any format seen fewer than twice: two posts is not a trend and a percentage from one post reads far more authoritative than it is.
posts_analysed is the real denominator for this account and varies: about 12 on average across the catalog, but some accounts hold 90 or more and some only a handful. Treat the split as a recent tendency rather than a complete history, and read posts_analysed before trusting a percentage.
avg_views is null for image formats, which have no view count at all.
Formats are Instagram's own product types translated into plain words: clips is a reel, carousel_container is a carousel. The raw value is returned on each post by the top-posts endpoint.

Parameters

Every value the call accepts, with the example the spec ships so the request runs as written.

Name	In	Required	Example	What it does
`handle`	path	required	`nasa`	Instagram handle, without the @.

Call it

Authenticate with a bearer token or the x-api-key header. Keys are server-to-server credentials. Never embed one in front-end code - call the API from your own backend and forward the result.

curl

curl "https://crmsolid.com/data-api/v2/insights/instagram/nasa/content-mix" \
  -H "Authorization: Bearer psk_live_..."

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/insights/instagram/nasa/content-mix", {
  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();

Python

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/insights/instagram/nasa/content-mix",
    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.

What comes back

Success is { data, meta }. Failure is { error: { code, message, request_id } }. The body below is the spec's own example: the values in it are illustrative readings, not live numbers.

Handle: nasa
User id: 528817151
Followers: 98,412,330
Posts analysed: 12
From: 6/2/2026, 11:20:00 AM
To: 8/29/2026, 6:41:00 PM
Account avg interactions: 412,907
Formats: 2 items

200 GET /insights/instagram/{handle}/content-mix

{
  "data": {
    "handle": "nasa",
    "user_id": "528817151",
    "followers": 98412330,
    "posts_analysed": 12,
    "from": "2026-06-02T11:20:00.000Z",
    "to": "2026-08-29T18:41:00.000Z",
    "account_avg_interactions": 412907,
    "formats": [
      {
        "format": "reel",
        "posts": 7,
        "share_pct": 58.3,
        "avg_likes": 512004,
        "avg_comments": 4120,
        "avg_views": 12884102,
        "vs_account_avg_pct": 25.1
      },
      {
        "format": "carousel",
        "posts": 5,
        "share_pct": 41.7,
        "avg_likes": 288311,
        "avg_comments": 2004,
        "avg_views": null,
        "vs_account_avg_pct": -29.6
      }
    ]
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42
  }
}

The meta block

request_idstringrequired
Unique id for this request. Quote it in a support ticket.
generated_atstringrequired
Server time the response was produced.
took_msintegerrequired
Milliseconds spent server-side.
pagePageoptional
sourcestringoptional
Which backend served the payload, for endpoints with more than one.
cache_age_sintegeroptional
Age of the underlying data in seconds. 0 for live reads.

When it fails

GET /insights/instagram/{handle}/content-mix documents 8 failure statuses. Branch on error.code, which is stable and enumerated; message is prose and may change.

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.
404NotFoundnot_found
The addressed resource does not exist.
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.

Coverage and limits

This endpoint covers Instagram. Rate limits come from the tier on your key.

Instagram

Tier	Requests a minute	Requests a day	Live reads a minute
free	30	1,000	5
standard	120	25,000	20
pro	600	250,000	60
unlimited	6,000	10,000,000	600

This call only draws on the ordinary per-minute and per-day columns. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

The rest of the Insights group

Derived engagement intelligence: engagement rates, top and viral posts, posting patterns and cohort benchmarks computed over the post layer.

Other groups

Accounts Directory X People Live scrape Trends Identity Graph Watch Research Tools Leads

Start calling it

A key takes a minute to mint in the panel, no card. The reference covers authentication, the envelope, scopes, rate limits and every error code in one page.

Get a key All 127 endpoints Full reference What the Data API is

Reference path: /data-api/reference/insights-instagram-content-mix