Modern API for your platform
OpenAPI 3.0, JSON, documentation with examples. Integration in a day.
Service scope and specifications
- Name
- REST API
- Purpose
- Programmatic access to all EPG Service data through a single REST API.
- Scope
- Schedule, metadata and channel endpoints; OpenAPI 3.0 documentation; sandbox for development.
- Target audience
- Pay TV, IPTV and OTT operators.
- Technical specs
- OpenAPI 3.0, JSON; API key authentication.
- Pricing
- Included in subscription / package (per contract).
- Delivery
- SaaS / API access under a services agreement.
The Problem
Old formats (XMLTV, FTP) are unreliable, hard to parse, no typing.
How it works
Modern REST API with JSON
OpenAPI 3.0 specification
Interactive documentation with examples
Test sandbox
Benefits
OpenAPI 3.0
Client generation, typing
JSON
Standard format for all platforms
Documentation
Interactive, with examples
< 200ms
Latency p95
More for operators
Schedules for 4K channels. Completeness, accuracy, real-time updates.
Genres, cast, studios, ratings, posters, stills.
All platforms speak one language. Recommendations work, reruns don't duplicate, TV and VOD are linked.
Every program start within ±3 sec accuracy. Catch-up opens right from the first frame.
EPG metadata translation for your audience's language. Works in your existing XMLTV/JSON integration. Languages: kz, en, more coming.
Content compliance with legislation. 6 risk categories, registry monitoring, age rating. Shared responsibility.
Channel broadcast geography. Which channel is available in which region.
Logos, descriptions, contacts, website, social media, broadcast language.
Sport type, championship, teams, persons + posters.
Stylized posters for sports broadcasts: team logos, tournament emblems, athlete portraits.
Full schedule by actual broadcast, not planned.
100% episodes filled. Better viewer experience, catch-up without duplicates, accurate recommendations.
Ad breaks and promos marked. For skip features.
Personal content recommendations based on viewer preferences.
Mapping linear TV and VOD catalog. Unified content space for recommendations.
Frequently asked questions
What is REST API and what is it for?
Programmatic access to all EPG Service data through a single REST API.
What does REST API include?
Schedule, metadata and channel endpoints; OpenAPI 3.0 documentation; sandbox for development.
In what formats is the data delivered?
OpenAPI 3.0, JSON; API key authentication.
How to connect REST API?
SaaS / API access under a services agreement.
How much does REST API cost?
Included in subscription / package (per contract).
Ready to connect REST API?
Tell us about your needs — we'll find the optimal solution.