API Documentation — Extended
Public and Protected APIs for Schedule, Channels, and playable pages. This page shows how to build iframe embeds, how to parse schedule JSON, and the known folder patterns.
Protected API (Key)
Secure API endpoints requiring API key. Contact support to get your API key
channels, schedule, or infoChannels JSON — `logo_url` (new)
Channels returned by the API now include a logo_url field. This value is either:
- Local path relative to daddy domain, e.g.
logos/espn.png - Absolute URL e.g.
https://example.com/logos/espn.png
https://dlstreams.top/logos/• The API tries to return a cached, server-hosted logo when available (preferred).
• If an external logo is blocked or unavailable we may return the original external URL instead — clients should be resilient.
• Logos may be PNG, JPG or SVG. When embedding into HTML, prefer using the
<img> tag and set a width/height or CSS constraints.
/cast/stream-<id>.php, /watch/stream-<id>.php, /plus/stream-<id>.php, /casting/stream-<id>.php, /player/stream-<id>.php.How to construct a playable URL & embed (iframe)
Use the channel channel_id and one of the supported folders. The player pages are full HTML pages that contain the video player.
stream-<id>.php (for example /cast/stream-302.php).Protected API Authentication & Usage
The protected API uses key.
• Valid API key in the
key parameter• Contact support to get your key
Schedule JSON structure (details)
The schedule JSON uses human readable day headers as top-level keys. Each header maps to an object of categories (e.g. "TV Shows", "Football"). Each category is an array of event objects.
Notes:
- Use the
channelsarray for primary playable channels.channels2may contain alternate sources or metadata — check for its presence before assuming it's empty. - Channel IDs are strings in the JSON (e.g. "302"). Treat them as identifiers — do not assume numeric sorting order unless you cast to int.
- Category keys may contain punctuation and spaces. When parsing server-side, iterate through keys rather than attempting to split them on a specific format.
Extra notes, folders & recommendations
- Folders & naming: the system supports multiple public player folders. When in doubt, try each folder using the same filename
stream-<id>.php(for example:/stream/stream-302.php,/cast/stream-302.php,/watch/stream-302.php, etc.). - If you plan to embed many players per page, open stream pages in a lightbox or only create an iframe when the user clicks to avoid many simultaneous connections.
- If a player page includes a cross-origin resource or requires cookies, ensure you add proper
allowattributes on the iframe and CORS headers on the player page. - Logos: cache logos on the server and return the server-hosted path whenever possible to avoid CORS/hotlinking issues and reduce external requests.
- If a channel's logo is missing a server-hosted copy, the API may return the original external URL — clients should handle both cases.
Contact / Support
If something is missing or the player pages behave differently across folders, contact: