Skip to main content
The Streamforge External API provides access to game metadata from IGDB (Internet Game Database) and allows you to find content related to specific games.

Game Endpoints

The API offers several endpoints for working with games:
  • GET /platforms/{platform}/games/{game_id} - Get game by platform ID
  • POST /platforms/{platform}/games/bulk - Get multiple games
  • GET /platforms/{platform}/games/{game_id}/content - Get content for a game
  • GET /games/search - Search games by name

Platform Support

Games are available on different platforms:
  • Twitch: Games are identified by Twitch game IDs
  • YouTube: Games are identified by YouTube game channel IDs
  • IGDB: Direct access using IGDB game IDs

Finding Games

Search by Name

The easiest way to find games is using the search endpoint:

Filter by Platform

Search for games available on a specific platform:

Game Data Structure

Games include IGDB metadata:
Key fields:
  • id: IGDB game ID (cross-platform identifier)
  • twitch_id: Twitch game ID (if available on Twitch)
  • youtube_id: YouTube game channel ID (if available on YouTube)
  • first_release_date: When the game was first released

Getting Games by Platform ID

Twitch Game ID

YouTube Game Channel ID

IGDB Game ID

Bulk Game Lookup

Fetch multiple games in a single request:

Getting Content for Games

Find streams and videos related to a specific game:

Content Filtering

Filter game content by various criteria:

Sorting Options

Sort game content by different statistics:
  • created_at - When content was created (default)
  • views - Total views
  • viewers - Peak concurrent viewers

IGDB Integration

Games are enriched with IGDB metadata. You can use IGDB IDs to:
  1. Fetch full game details from IGDB API (cover art, ratings, genres, etc.)
  2. Cross-reference games across platforms
  3. Get comprehensive metadata not available in the Streamforge API

Example: Using IGDB ID

Use Cases

Game Content Discovery

Cross-Platform Game Analysis

Best Practices

Use game search to find games by name, then use the returned IDs for subsequent requests. This is more reliable than guessing platform-specific IDs.
  • Search first: Use /games/search to find games by name
  • Store IGDB IDs: IGDB IDs are cross-platform identifiers
  • Filter by platform: Use platform filters when you only need games from one platform
  • Paginate content: Use cursor pagination for large content lists
  • Cache game data: Game metadata doesn’t change frequently

Limitations

  • Games only on Twitch/YouTube: Game content endpoints only work for Twitch and YouTube
  • IGDB platform: When using platform=igdb, you can’t fetch content (games don’t have content on IGDB)
  • Search limits: Search returns up to 100 results per query
Game content endpoints (/games/{game_id}/content) only work for Twitch and YouTube platforms, not IGDB.