Sprout Social API in 2026: What It Returns, What It Costs, and Where Twitter (X) Data Runs Out

Sprout's documentation (api.sproutsocial.com/docs) opens with the scope in one sentence: the API exists "to access your owned social profile data so you can use that data to power dashboards and automate your reporting." Everything below follows from that. Each request path carries your Sprout customer ID (/v1/<customer_id>/<endpoint>), and analytics requests filter on the customer_profile_id values of profiles connected to your account.

The "does not include" list. The same overview names three exclusions: paid (ad account) data, Listening data from X, and message-level Listening data from Reddit. The X metrics section repeats it: "X data is not available for Listening endpoints." So the Listening endpoints can return earned-media results for other networks, but not for X.

The X metrics you do get (owned profiles only). For an X profile you connect, the owned-profile metrics include followers (lifetime_snapshot.followers_count), net follower growth, impressions, video views, likes, @replies, reposts, post link clicks and posts sent. Several more (media views, media clicks, hashtag clicks, profile clicks, detail expands, app installs) are marked "Premium Analytics Required". Sprout computes engagements as likes + @replies + reposts + post link clicks + other post clicks + other engagements, and offers engagement rate per follower and per impression.

Shape limits worth knowing before you build. Analytics requests accept up to 100 profiles each, a reporting_period of at most one year, and responses are capped at 10,000 results with cursor pagination beyond that. Message lookups by ID accept up to 100 per request.

Sprout does not sell API access on its own, and it does not publish a per-call price. The developer docs state the prerequisite without naming a tier: "Your account needs to be on the appropriate plan which enables API access. If you are unsure, please contact your sales representative or contact support." Sprout's pricing page (sproutsocial.com/pricing) is where the tier shows up.

Sprout's own blog post on its API (sproutsocial.com/insights/sprout-social-api) says the same in plainer words: the Public API "is available to all Advanced Plan customers." The pricing page shows prices under an "Annual billing" heading; only Essentials lists a separate month-to-month price.

Add-ons that change what the API returns. Premium Analytics and Listening "are each available as individual add-ons to the Standard plan and up", and neither add-on price is published (the page routes to "Schedule a demo"). Premium Analytics matters for the API because the X metrics marked "Premium Analytics Required" come back only with it, and Sprout's Tableau connector needs "Premium Analytics add-on along with the Sprout Advanced Plan".

What we could not verify. Sprout's support article on API access (support.sproutsocial.com/hc/en-us/articles/360045006152) returned a browser challenge to every automated fetch this session, so this page relies on the developer docs and the pricing page for the plan requirement. If your contract predates the current plan names, ask Sprout support which tier your seats map to.

Rate limits. The docs list two numbers and no burst allowance: 60 requests per minute and 250,000 requests per month. Over the limit the API answers 429 Too Many Requests. For a reporting job that pulls 100 profiles per analytics call, 60 a minute is plenty; for anything shaped like data collection it is a ceiling.

Authentication. Two options, both sent as Authorization: Bearer <token>. OAuth 2.0 is the recommended path: Sprout issues short-lived JWT access tokens, with the client_credentials grant for machine-to-machine jobs and the authorization code flow for user-based integrations. The alternative is an API token that a user with the API Permissions permission generates under Settings > Global Features > API.

The X-specific gate. Before any X data comes through, a Sprout user with API permissions has to accept the "Sprout API X Content End User License Agreement", and the metrics section adds that "Customers are required to undergo a brief X review and approval process before being able to access their X data through the Sprout Analytics API." Plan the approval into your timeline; Sprout's docs mention the case where "X does not approve your specific use case".

Teams usually hit the gap with one of three requests. Each needs data about X accounts that are not connected to your Sprout account, and none of them is answered by an owned-profile API.

"Benchmark us against three competitors, every week, in our own dashboard." Sprout's app has competitor reports (the pricing page lists "extensive competitor, tag and paid insights" on Professional), but the Public API's analytics endpoints filter on your own customer_profile_id values. A competitor's handle is not a profile you can connect, so its posts and engagement do not come back through the API.

"Track every post that mentions our product on X." That is Listening, and Sprout's docs list "Listening data from X" as not included in the API. So X mentions cannot be exported through the API.

"Pull the followers of an account, or search X for a keyword." No endpoint in the Sprout API returns follower lists or arbitrary search results. Those are X data operations, which is what X's own API and third-party X data APIs exist for.

When Sprout remains the right tool. If the job is publishing, inbox, care cases and reporting across Facebook, Instagram, LinkedIn, TikTok, Pinterest and YouTube as well as X, Sprout's multi-network suite remains a fit, and its API is how you get that owned data into a warehouse. Impressions and link clicks for your own posts also only exist in owner-side analytics; no public data source returns them.

When a pay-per-call X data API fits. Anything about accounts you do not own: competitor cadence and engagement, mention streams, keyword searches, follower lists, historical timelines. With TwitterAPI.io those are plain GET requests (/twitter/user/info, /twitter/user/last_tweets, /twitter/tweet/advanced_search, /twitter/user/followers, /twitter/user/mentions) billed per result, with no seat and no plan gate. The study below is exactly that kind of job.

We pulled the public profile and the 100 most recent posts (replies excluded) of 13 brand accounts with 84M followers between them, then computed what a social team usually wants from a competitor benchmark: posting cadence, median public engagements per post (likes + reposts + replies + quotes, reposts excluded because their counters belong to the original post) and engagement per post per 1,000 followers. Sprout's and Hootsuite's own accounts are in the set.

The spread is the story. Median engagement per post per 1,000 followers ranges from 2.559 for @Duolingo to 0.004 for @hootsuite, a 640x gap. Raw follower count predicts little: @netflix has 29.3M followers and a median of 2,982 engagements per post, while @Duolingo, with 1.0M, gets 2,685.

Cadence varies by two orders of magnitude. The median account posted 3.2 times a week over the last 90 days; @netflix posted 113 a week, @NotionHQ 33.4 (59% of its sample were reposts). Two of the 13, @Starbucks and @SproutSocial itself, posted nothing in the last 90 days: their latest posts were 619 and 119 days old at collection time.

Views tell a second story. The public viewCount lets you compute engagements per 1,000 views for any account, a rough public stand-in for Sprout's engagement rate per impression: @Duolingo's median was 15.43, @hootsuite's 2.05. It is not the same metric (Sprout's impressions come from X's owner-side analytics and its engagements include link clicks), so use it for comparing accounts, not for matching a Sprout report.

The fair comparison is not "Sprout vs raw data" but which metrics live where. Owner-side analytics see things the public never does; public data covers every account, not just yours.

Practical split. Keep Sprout (or any owned-analytics source) for impressions and clicks on your own posts, and pull the public layer for your own account and every competitor from an X data API, so the benchmark compares like with like. In our study, a full re-pull of one competitor (profile plus 100 posts) costs $0.01518.

A pay-per-call X data API is not a replacement for Sprout's publishing, inbox or multi-network reporting, and this page does not pretend it is. It replaces the part Sprout's API does not do: reading X itself. The costs below use TwitterAPI.io's published per-result prices and X's own pay-per-usage rate card (docs.x.com/x-api/getting-started/pricing).

Per 1,000 posts that is $5 on X's rate card against $0.15 here, about 33x. X's pay-per-usage plan is also capped at 3 million post reads per monthly billing cycle, with Enterprise above that; new X API customers get $20 in credits on a first eligible card and a match of the first auto-recharge up to $50.

How the monthly figure is built. One /twitter/user/last_tweets call and one /twitter/user/info call per account per day. A day with no new post still costs the 15-credit request minimum ($0.00015), and a full 20-post page costs $0.003. At the cadences we measured, timelines come to $0.16 a month and daily profile snapshots (which give you net follower growth) $0.07.

Getting started. New accounts that pass the automatic bot check get up to $1 of free credits (at most 100,000 credits, no card, one per person or network, expiring after 31 days). Purchased credits never expire; $1 = 100,000 credits. Subscriptions start at Starter $29 a month (then Builder $99, Pro $199, Scale $499, Business $1,499) for teams that want higher rate limits; see the pricing page for what each includes.

The script in the code block at the end of this page is the study above in about 80 lines: one /twitter/user/info call per handle (followers), up to five /twitter/user/last_tweets pages of 20 posts (cadence and engagement), then the same medians we report. It reads only the fields the API returns: followers, userName, createdAt, likeCount, retweetCount, replyCount, quoteCount, viewCount, plus has_next_page and next_cursor for paging.

Two details that bite. An unknown handle does not return 404: /twitter/user/info answers HTTP 200 with status: "error" and msg: "user not found", so check status before reading data. And skip reposts when measuring engagement: a repost's counters belong to the reposted post, which would credit a brand with someone else's reach.

Where to put it. Run it on a daily schedule and append rows to the same table your Sprout API export lands in, keyed by handle and date. Your own account then has both layers (owner-side impressions from Sprout, public engagement from X), and competitors have the public layer, which is the only one anyone outside those companies can see.

If you also publish. Posting to X through TwitterAPI.io is a separate, authenticated flow: one /twitter/user_login_v2 login ($0.10, with a proxy you supply) returns login_cookies, then each post via /twitter/create_tweet_v2 costs $0.002. Those calls act as that account, so X can rate-limit, lock or suspend it; keep a human pace, expect the session to need re-login occasionally, and note that billing is per HTTP 200 call.

"Hootsuite API" searches land on the same question, and the answer has the same shape. Hootsuite's developer docs (developer.hootsuite.com) describe a REST API with OAuth 2.0 that "operates on the same data" as the Hootsuite dashboard. Access needs an active Hootsuite user and an approved Developer account.

What it covers. A Publishing API that schedules posts with media (TikTok, YouTube and Bluesky are listed as not supported), a User Management API using SCIM, an Ow.ly link API for Enterprise users only, the Amplify employee-advocacy API, Inbox 2.0 APIs, and an Analytics API marked "New for April 2026" that returns posts with lifetime metrics and daily profile metrics. Using the Analytics API requires the user to have purchased the Advanced Analytics add-on and the app to request the analytics:read scope; its list endpoints accept a lastModified at most 30 days in the past.

Rate limits. Hootsuite's REST APIs allow 20 requests per second up to 100,000 calls per day, reported in X-Account-Quota headers, with 429 on overflow.

The same gap. Like Sprout's, Hootsuite's API works on the social profiles connected to a Hootsuite account. It is a way to automate Hootsuite, not a way to read arbitrary X profiles, timelines, followers or search results. If the reason you looked up either API is X data about accounts you do not own, the X data path in this page applies to both.

Question. For a set of public brand accounts, what can anyone compute from raw X data (followers, posting cadence, public engagement per post and per 1,000 followers, views), and which owner-side numbers in a Sprout report can public data not reproduce?

Accounts. @Wendys, @Duolingo, @netflix, @Spotify, @Nike, @Starbucks, @Airbnb, @Adobe, @Canva, @NotionHQ, @Shopify, @SproutSocial and @hootsuite: 13 organization accounts chosen as recognizable brands with active social teams, plus the two social-suite vendors.

Window and sample. Collected in 2026. One /twitter/user/info call and five pages of /twitter/user/last_tweets (replies excluded, newest first) per account: 1,300 posts and 13 profiles in 78 requests, $0.20 at list prices. Each account's window is the span its 100 most recent posts cover, from 6.2 days (@netflix) to 903 days (@Adobe). Posts per week use the last 90 days, or the shorter span when 100 posts do not reach back that far.

What the sample cannot show. Impressions, link clicks and profile clicks are owner-only analytics, so we cannot reproduce Sprout's engagement rate per impression; viewCount is a public proxy, not the same number. Engagement counts are cumulative at collection time, so the newest posts are still accruing. 100 posts is a recent snapshot, not a year of history, and 13 brands are not a representative sample of all brands.

Privacy. Aggregates only, organization accounts only; no reposted, quoted or replying authors are analyzed. Raw pages are kept compressed for audit because every account is an organization account.