Fetch keyword web citation and sentiment analytics as structured JSON with one SocialCrawl API key. Analytic reads cost 20 credits. Reference lists cost 1 credit. This is web mention intelligence, not a social scrape.
10 active endpoints. Web citation and sentiment analytics.
GET /v1/content_analysis/search
GET /v1/content_analysis/summary
GET /v1/content_analysis/sentiment
GET /v1/content_analysis/rating-distribution
GET /v1/content_analysis/phrase-trends
GET /v1/content_analysis/category-trends
GET /v1/content_analysis/languages
GET /v1/content_analysis/locations
GET /v1/content_analysis/categories
GET /v1/content_analysis/filters
What Content Analysis endpoints does SocialCrawl ship?
Ten live GET endpoints for keyword-based web citation intelligence. Search mentions, roll up summaries, score sentiment, trend phrases and categories, and load reference taxonomies. Data API only. Not native social posts or comments.
Pages across news, blogs, shops, and message boards that mention your keyword. Each row carries sentiment and emotional tone. Cursor-paginated for deeper pages.
Ten-bucket histogram of ratings found in a keyword's web mentions, with sentiment, domains, and categories per bucket. Built for review-heavy products and terms.
// Running this live needs your own API key. Hit "Try it" to see an example response
How the Content Analysis API works
Content Analysis is a normal SocialCrawl analytics surface. You call GET /v1/content_analysis/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second analytics vendor SDK.
Authenticate every call
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog. No second vendor key on your side.
GET with query params
All public routes are GET. Pass keyword, category_code, date ranges, filters, limit, and cursor as query strings. We validate formats before charging.
Pay in credits, not seats
Analytic GETs cost 20 credits. Reference lists cost 1 credit. Cache hits cost 0. Empty or hard failures refund. Bad params never charge.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists may also carry pagination cursors.
The usual integration chain
Most products load reference maps once, size a keyword with summary or sentiment, then page mentions or trends only when the signal is worth it.
01Reference
GET /v1/content_analysis/filters
Languages, locations, categories, and filter field maps
Resolve codes and valid filters before analytic spend.
02Size
GET /v1/content_analysis/search?keyword=…
Summary or sentiment roll-up for the keyword
One call characterizes volume and tone before you page raw mentions.
03Mentions
GET /v1/content_analysis/summary?keyword=…
Paginated citation search with per-page sentiment
Read individual pages when the roll-up is not enough.
04Trends
GET /v1/content_analysis/phrase-trends?keyword=…&date_from=…
Phrase or category time series over a date range
Track movement after you know the baseline snapshot.
request
GET /v1/content_analysis/search
?keyword=socialcrawl
&page_type=news
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
# aggregate
GET /v1/content_analysis/summary?keyword=socialcrawl
GET /v1/content_analysis/sentiment?keyword=socialcrawl
Content Analysis uses Analytics-shaped payloads under the shared SocialCrawl envelope. This is citation intelligence, not Post or Comment leaves from social platforms.
Analytics / Trends and refslanguages, locations, categories, filters
time-series buckets for phrases or categories; static language, location, category, and filter maps
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint. Content Analysis is not a sidecar.
01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency per key.
02
Validate, then debit
Registry lookup finds content_analysis routes. Required params run first. Invalid input returns 400 with no charge. Valid calls debit 20 or 1 credits before upstream work.
03
Cache or fetch
A deterministic cache key is built from platform, resource, and params. Hit: return immediately, credits_used = 0. Miss: analytic GETs run as live content-analysis jobs; reference lists map to static lookups and cache heavily.
04
Normalize and return
Upstream JSON is shaped into Analytics payloads, wrapped in the success envelope, and logged for billing audit. Field maps stay passthrough Analytics rather than social Post leaves.
Billing rules that matter in production
Analytic live miss: 20 credits
Reference list live miss: 1 credit
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Search page size capped for the flat 20-credit fee
Paginate mentions with cursor for more rows
Same key as the rest of the catalog
How we get the data
Content Analysis is keyword web citation and sentiment analytics over a large mention database. It is not a scrape of TikTok, X, or other social timelines.
What Content Analysis is for this API
Web-wide brand and keyword listening: news, blogs, shops, message boards, and organization pages. Read-only analytics for research, monitoring, and product jobs.
How SocialCrawl reaches it
Public GETs map to live content-analysis jobs for analytics and to static reference lookups for languages, locations, categories, and filters.
What leaves our edge
A unified JSON envelope: success, data, credits_used, request_id, cached. Mentions carry sentiment axes. Rollups and trends stay under Analytics shapes.
What we do not ship
No social platform post scrape on this surface. No write endpoints. No vendor dashboard login. Native social reads live under their own platform routes.
aggregate rolls→ summary / sentiment / ratingsummary totals, country and language splits, rating buckets
time series→ phrase-trends / category-trendsphrase and category time series; taxonomy and filter maps
What this API is used for
The jobs this API is most often used for.
10active Content Analysis endpoints in the registry
20 / 120-credit analytics vs 1-credit reference
Brand mention sizing and web sentiment
Callers concentrate on summary and sentiment first, then search pages for evidence. Trends and rating distribution show up for longer brand tracking jobs. Keyword web citation analytics with six-axis sentiment under the same SocialCrawl key and envelope as social platforms. Flat 20-credit analytic tier. Reference maps at 1 credit.
Analytic live jobs are slower than cached reference lists. Reference endpoints are heavily cached and usually return quickly after the first miss.
What people build with the Content Analysis API
The jobs Content Analysis data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
It is a web-wide brand-mention and sentiment API. For any keyword it returns every web page that cites the term: news, blogs, ecommerce, message boards, organization sites, each scored on a 6-axis emotion model plus positive/negative/neutral probabilities, all as unified JSON on one x-api-key.
Does it return social media posts or web page mentions?
Web page mentions, not native platform posts. The content analysis API works over a cross-web citation database, so results are page-level (URL, domain, snippet, sentiment) rather than individual tweet or post IDs. For native posts, use SocialCrawl's per-platform endpoints instead.
What endpoints does the content analysis API have?
10 endpoints: Search, Summary, Sentiment, Rating Distribution, Phrase Trends, Category Trends, Languages, Locations, Categories, and Filters. Each is a GET at /v1/content_analysis/{resource}.
How is sentiment scored in the brand mention data?
Sentiment is model-derived NLP, not ground truth. Each mention carries a 6-axis emotion split (anger, happiness, love, sadness, share, fun) and positive/negative/neutral probabilities. SocialCrawl passes the model output through verbatim so you can apply your own thresholds.
How much does the content analysis API cost?
Analytic endpoints (search, summary, sentiment, trends) cost 20 credits each on the advanced tier; reference lookups (languages, locations, categories, filters) cost 1 credit. New accounts get 100 free credits with no credit card required, so you can test before paying.
What is the best API for social media sentiment analysis?
For web-wide mention sentiment, SocialCrawl's content analysis API covers it in 10 endpoints: each mention carries a 6-axis emotion split plus positive/negative/neutral probabilities, at 20 credits per analytic call. For sentiment on native social posts, pair it with the per-platform endpoints: same key, same JSON envelope, 100 free credits to start.
Does SocialCrawl offer a content analysis data API?
Yes, SocialCrawl is that content analysis data API. There is no single official API for reading web-wide brand mentions, so instead of stitching together a crawler and an NLP model you call 10 endpoints: a paginated mention search, summary and sentiment rollups, a rating histogram, phrase and category trends, and reference lookups. Every mention carries a 6-axis emotion split and positive/negative/neutral probabilities in one unified JSON envelope, from 20 credits per analytic call.
Is scraping Content Analysis data legal?
SocialCrawl returns publicly available Content Analysis data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with Content Analysis's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Content Analysis scraping API vs the official Content Analysis API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Content Analysis endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.