How it works
By default, article endpoints return base fields only — lightweight and fast. To get enriched data like sentiment analysis, entity extraction, or market impact, use theinclude query parameter.
Available modules
| Module | Fields | Min Plan |
|---|---|---|
sentiment | sentimentScore, sentimentLabel, sentimentConfidence | Pro |
market_impact | marketImpactLevel, marketImpactHorizon, marketImpactScope, marketConfidenceLevel | Pro |
entities | entities[] with mentionCount, prominenceScore, sentimentTowardEntity, isInTitle, isInLead | Pro |
translations | titlePt, subtitlePt, summaryPt, titleEn, subtitleEn, summaryEn | Starter |
scoring | baseScore, sourceScore, depthScore, exclusivityScore, financialImpactScore, typeMultiplier | Pro |
classification | secondarySectors[], secondaryTopics[] | Starter |
meta | sourceTier, hasPaywall, wordCount, readingTimeMin, authorName | Starter |
Base fields (always returned)
These fields are included in every response regardless of theinclude parameter:
Enriched response example
With?include=sentiment,entities,scoring:
Plan-gated modules
If you request a module your plan does not include, the API returns403:
Best practices
- Request only what you need. Each module adds data to the response. Smaller payloads mean faster responses.
- Cache enriched responses. Sentiment, entities, and scoring don’t change after classification. Cache them on your side.
- Use base fields for listing, enriched for detail. List endpoints with base fields, then fetch individual articles with
includewhen the user clicks through.