Connected content for recommendations
Unique IDs for content, series, persons. Linked to Kinopoisk, IMDB.
Service scope and specifications
- Name
- Content IDs
- Purpose
- Unified content identification across platforms and sources.
- Scope
- Unique IDs for films, series, episodes and persons; linkage to external catalogs; catch-up deduplication and TV/VOD linking.
- Target audience
- Platform vendors and integrators.
- Technical specs
- REST API, JSON; mapping to Kinopoisk, IMDB and others — per contract terms.
- Pricing
- From 50,000 RUB/mo (depends on volume — specified in the contract).
- Delivery
- SaaS / API access under a services agreement.
The Problem
Recommendations for your clients work poorly — content is not linked, no unified IDs, duplicates.
How it works
Get unique IDs for each content unit
Links: movie → series → person → genre
Mapping to Kinopoisk, IMDB
API for search and navigation
Benefits
Recommendations
ML works when content is connected
Deduplication
One movie = one ID across all channels
Navigation
Viewer found actor → all their movies
External links
Kinopoisk, IMDB, Wikidata
Data Structure
Complete metadata for movie, series or show
Core Fields
Includes
More for vendors
Schedules for 4K channels. Completeness, accuracy, real-time updates.
OpenAPI 3.0, JSON, clear endpoints.
Genres, cast, studios, ratings, posters, stills.
Logos, descriptions, contacts, website, social media, broadcast language.
Channel broadcast geography. Which channel is available in which region.
Channel list by operator/provider. For TV guides and navigation.
Mapping linear TV and VOD catalog. Unified content space for recommendations.
Connect LLM to metadata. AI-powered discovery.
Test environment with real data.
Python, JavaScript — ready libraries.
Frequently asked questions
What is Content IDs and what is it for?
Unified content identification across platforms and sources.
What does Content IDs include?
Unique IDs for films, series, episodes and persons; linkage to external catalogs; catch-up deduplication and TV/VOD linking.
In what formats is the data delivered?
REST API, JSON; mapping to Kinopoisk, IMDB and others — per contract terms.
How to connect Content IDs?
SaaS / API access under a services agreement.
How much does Content IDs cost?
From 50,000 RUB/mo (depends on volume — specified in the contract).
Ready to connect Content IDs?
Tell us about your needs — we'll find the optimal solution.