Profile IDs
Profile IDs are platform-specific creator identifiers:Twitch
- Format: Numeric string (e.g.,
"484563826") - How to find: Twitch channel URL or API
- Example:
https://twitch.tv/streamer123→ Channel ID484563826
YouTube
- Format: Channel ID string (e.g.,
"UCaY_-ksFSQtTGk0y1HA_3YQ") - How to find: YouTube channel URL or API
- Example:
https://youtube.com/@channel→ Channel IDUCaY_-ksFSQtTGk0y1HA_3YQ
TikTok
- Format: Numeric string (e.g.,
"1234567890") - How to find: TikTok profile URL or API
- Note: TikTok IDs may change; use display names for stability
- Format: Numeric string (e.g.,
"1234567890") - How to find: Instagram profile data or API
- Note: Instagram user IDs are stable numeric identifiers
Content IDs
Content IDs identify individual streams, videos, or posts:Twitch
- Format: Numeric string (e.g.,
"324628972153") - Type: Video ID or stream ID
- Example:
https://twitch.tv/videos/324628972153
YouTube
- Format: Alphanumeric string (e.g.,
"dQw4w9WgXcQ") - Type: Video ID
- Example:
https://youtube.com/watch?v=dQw4w9WgXcQ
TikTok
- Format: Numeric string (e.g.,
"7123456789") - Type: Video ID
- Example:
https://tiktok.com/@user/video/7123456789
- Format: Post shortcode (e.g.,
"CxYz123AbCd") - Type: Post/Video ID
- Example:
https://instagram.com/p/CxYz123AbCd - Note: Instagram uses alphanumeric shortcodes in URLs
Game IDs
Game IDs vary by platform and can reference IGDB data:Twitch Game ID
- Format: Numeric string (e.g.,
"2011938005") - Source: Twitch’s game taxonomy
- Example: Used in
GET /platforms/twitch/games/{game_id}
YouTube Game Channel ID
- Format: Channel ID string (e.g.,
"UCf_7CrLpgmot2vPKYwx5zQg") - Source: YouTube’s game channel taxonomy
- Example: Used in
GET /platforms/youtube/games/{game_id}
IGDB Game ID
- Format: Numeric string (e.g.,
"189165") - Source: IGDB (Internet Game Database)
- Example: Used in
GET /platforms/igdb/games/{game_id} - Note: IGDB IDs are cross-platform identifiers
Finding Profile IDs
Twitch
YouTube
TikTok
Cross-Platform Matching
The Socials endpoint provides cross-platform matching:ID Validation
The API validates IDs but doesn’t provide validation endpoints. To verify IDs:- Make a request: Try fetching the resource
- Check response: 404 means invalid or non-existent ID
- Handle gracefully: Missing resources are normal
Best Practices
- Store IDs, not URLs: URLs can change; IDs are stable
- Validate before bulk requests: Check IDs exist before bulk operations
- Use socials data: Leverage cross-platform socials data for multi-platform workflows
- Handle missing IDs: Some IDs may not exist; handle 404s gracefully
- Document ID sources: Keep track of where IDs come from for debugging
Normalized Terminology
The API normalizes platform-specific terminology to provide consistency across all platforms.This normalization only applies to equivalent concepts. On YouTube, “subscribers” represents the free channel subscription count and maps to
followers. On Twitch, followers remains followers - the separate paid “subscriber” concept is not exposed through this field.
