Skip to main content
Learn how to fetch, filter, and analyze content (streams, videos, and posts) from creators and platforms.

Content Endpoints

The API provides several ways to access content:
  • GET /platforms/{platform}/content/{content_id} - Get single content item
  • GET /platforms/{platform}/content - List all content for a platform
  • GET /platforms/{platform}/profiles/{profile_id}/content - List content by creator
  • GET /platforms/{platform}/games/{game_id}/content - List content for a game
  • POST /platforms/{platform}/content - Get multiple content items

Content Types

Content types vary by platform:
Instagram stories are only available via direct ID lookup and are excluded from list operations. Story availability is limited and depends on internal data collection processes - do not expect comprehensive story coverage for any given creator.

Getting Content by Creator

Fetch all content from a specific creator:

Content statistics

Content items include detailed statistics:

Understanding Statistics

  • statistics.views.sum: Total view count
  • statistics.viewers.avg: Average concurrent viewers (for streams)
  • statistics.viewers.max: Peak concurrent viewers
  • statistics.watched_minutes.sum: Total watch time in minutes
  • duration: Content duration in milliseconds

Analyzing Content Performance

Calculate Average Views

Find Top Performing Content

Calculate Engagement Rate

Time-Based Analysis

Filter by Date Range

Platform-Specific Features

Twitch Chapters

Twitch streams include aggregated chapter data:
Analyze chapter performance:

Categories and Tags

Content includes categories (games) and tags:
Find most common games:

Content Comparison

Compare Creators

Compare Time Periods

Best Practices

Use bulk endpoints when fetching multiple content items. It’s more efficient than individual requests.
  • Paginate efficiently: Use appropriate limit values (10-50) based on your needs
  • Cache content data: Content metrics don’t change frequently; cache for performance
  • Filter client-side: Use date ranges and filters to reduce unnecessary requests
  • Handle missing metrics: Some content may not have all metrics; handle nulls gracefully
  • Monitor quota: List endpoints consume quota per item returned

Use Cases

Content Performance Dashboard

Content Discovery

Content list endpoints consume quota equal to the number of items returned. Use appropriate limit values to manage quota usage.