100 free credits. No credit card required.Start building
Logo
Content Analysis logoContent Analysis API

Run content analysis with one API

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.

Content Analysis logo
/v1/content_analysis

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.

Citation search

20 credits
/v1/content_analysis/search

Pages across news, blogs, shops, and message boards that mention your keyword. Each row carries sentiment and emotional tone. Cursor-paginated for deeper pages.

keyword, page_type, search_mode, limit, cursor, order_by, filters

Mention summary

20 credits
/v1/content_analysis/summary

One roll-up of every web mention of a keyword: total count, top domains, sentiment splits, and breakdowns by page type, country, and language.

keyword, page_type, positive_connotation_threshold, filters

/v1/content_analysis/sentiment

Two sentiment views of a keyword's web mentions: positive, negative, and neutral, plus six emotional axes such as anger, happiness, and love.

keyword, page_type, positive_connotation_threshold, filters

/v1/content_analysis/rating-distribution

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.

keyword, page_type, filters

Phrase trends

20 credits
/v1/content_analysis/phrase-trends

Time series of how often a keyword was mentioned on the web and how sentiment moved, one row per day, week, or month.

keyword, date_from, date_to, date_group, page_type, filters

Category trends

20 credits
/v1/content_analysis/category-trends

Same volume and sentiment time series as phrase-trends, keyed on a content category code instead of a keyword. Look up codes with categories first.

category_code, date_from, date_to, date_group, filters

Languages

1 credit
/v1/content_analysis/languages

Supported languages with names and ISO codes. Use them to filter calls or interpret language fields on mentions.

(none)

Locations

1 credit
/v1/content_analysis/locations

Supported locations for content analysis. Use them to interpret country fields on mentions or check coverage.

(none)

Categories

1 credit
/v1/content_analysis/categories

Full content category taxonomy with code, name, and parent code. Required input map for category-trends and for decoding mention categories.

(none)

/v1/content_analysis/filters

Fields you may filter on and the value type each accepts. Build a valid filters expression before search, summary, or sentiment.

(none)

Content Analysis API10 endpoints supported
View docs

Returns pages across news, blogs, shops, and message boards that mention your keyword, each scored for sentiment and emotional tone.

Use it to read the individual mentions and page through them; for one roll-up per keyword use summary instead.

20 credits

GET/v1/content_analysis/search?keyword=openai&search_mode=as_is&limit=10

keyword · Brand or term to find mentions of. Wrap in escaped double-quotes for an exact phrase (e.g. "logitech mouse").

$ curl https://www.socialcrawl.dev/v1/content_analysis/search?keyword=openai&search_mode=as_is&limit=10 \
    -H "x-api-key: sc_YOUR_API_KEY"
idle
// 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
response envelope
{
  "success": true,
  "data": {
    "items": [
      {
        "url": "https://example.com/article",
        "title": "Example citation",
        "sentiment": "positive",
        "published_at": "2026-07-01T00:00:00.000Z"
      }
    ]
  },
  "credits_used": 20,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Content Analysis uses Analytics-shaped payloads under the shared SocialCrawl envelope. This is citation intelligence, not Post or Comment leaves from social platforms.

Envelopesearch

success, data, credits_used, credits_remaining, request_id, cached

Analytics / Mentionssummary, sentiment, rating-distribution

citation rows with page metadata, sentiment scores, emotional axes, domains, categories, language, country

Analytics / Rollupsphrase-trends, category-trends

totals, domain splits, sentiment ratios, page-type and geo breakdowns, rating histograms

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

field map sketch
web citationssearch items + sentiment axeskeyword mentions, domains, page types, sentiment axes
aggregate rollssummary / sentiment / ratingsummary totals, country and language splits, rating buckets
time seriesphrase-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.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Brand listening teams

Python, cron, Slack bots

Run summary and sentiment on brand terms on a schedule. Open search when volume or tone shifts and evidence pages are needed.

Product research

Node, notebooks, BI loads

Use rating-distribution and phrase-trends for review-heavy terms. Join category-trends after resolving codes from categories.

Backend product jobs

Go, workers, Explorer

Load filters and taxonomies once, then wire analytic GETs into pipelines. Same API key as the rest of SocialCrawl.

Call it in two lines

Analytic routes cost 20 credits per live call. Reference lists cost 1. Cache hits are free. Start with keyword on summary or search.

curl "https://www.socialcrawl.dev/v1/content_analysis/search?keyword=socialcrawl" \
  -H "x-api-key: sc_your_api_key_here"
curl "https://www.socialcrawl.dev/v1/content_analysis/summary?keyword=socialcrawl" \
  -H "x-api-key: sc_your_api_key_here"
Content Analysis logoContent Analysis on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the Content Analysis API return?

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.

Comparison

How does SocialCrawl compare to Build-your-own NLP pipeline for Content Analysis data?

Same Content Analysis data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Setup

SocialCrawl
One GET per question: mentions, sentiment, and trends are each a single call
Build-your-own NLP pipeline
Crawler, mention index, and NLP models to build, train, and host

Coverage

SocialCrawl
Web-wide citation database: news, blogs, ecommerce, message boards
Build-your-own NLP pipeline
Limited to whatever your crawler reaches and you can afford to store

Sentiment scoring

SocialCrawl
6-axis emotion model plus positive/negative/neutral probabilities, passed through verbatim
Build-your-own NLP pipeline
Model selection, training data, and accuracy tuning are all on you

Pricing

SocialCrawl
20 credits per analytic call, 1 credit per reference lookup; 100 free credits to start
Build-your-own NLP pipeline
Compute, storage, and data engineering time before the first result

Maintenance

SocialCrawl
Endpoints stay stable behind the unified schema
Build-your-own NLP pipeline
Crawlers and models drift: retraining and fixes never stop
FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What is the SocialCrawl content analysis API?
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.

Ask AI about SocialCrawl

Read the Content Analysis API reference in the docs

🤖 AI agent or LLM? Read this page as markdown