Public REST API
Read-only JellyTV service status and product capability data with structured JSON errors.
Open API index ›Predictable, machine-readable entry points for learning what JellyTV is and querying its public, read-only discovery surface.
Read-only JellyTV service status and product capability data with structured JSON errors.
Open API index ›Typed operations, unique operation IDs, response schemas, descriptions, and reusable error definitions.
View openapi.json ›A stateless Streamable HTTP endpoint with read-only status, capabilities, and discovery tools.
View MCP discovery ›Canonical LLM guidance, indexable routes, and content negotiation on public pages.
View llms.txt ›The documented REST endpoints provide public product information in read-only mode. The MCP server offers public discovery tools and, where enabled, OAuth-protected tools for the signed-in user’s account, tickets, and synced Jellyfin server metadata.
For support or integration questions, email help@jellytv.app.
Each public REST endpoint allows 60 requests per 60 seconds per client. Responses publish the current IETF RateLimit-Policy and RateLimit fields, plus RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and X-RateLimit-* compatibility fields. A 429 Too Many Requests response also includes Retry-After in seconds.
Stable API versions use the URL path, such as /api/v1. Backward-compatible fields may be added within a version; breaking changes require a new versioned path. No public endpoint is currently deprecated.
A planned retirement will be announced at least 90 days in advance through the OpenAPI specification and this page. Affected responses will use the RFC 9745 Deprecation header and deprecation link relation, followed by the RFC 8594 Sunset header when a retirement date is set. Urgent security or legal changes may require a shorter period.