Build with DLive API

Supported endpoint values are channels, schedule, and info. Contact API support to request a key.

fetch('https://dlive.sx/daddyapi.php?key=YOUR_KEY&endpoint=channels')
  .then(response => {
    if (!response.ok) throw new Error('HTTP ' + response.status);
    return response.json();
  })
  .then(result => {
    if (!result.success) throw new Error(result.message || result.error || 'API error');
    console.log('Channels:', result.data);
    console.log('Total:', result.count);
  })
  .catch(error => console.error('Request failed:', error));

The URL builder above only creates a URL in your browser; it does not send a request or save your key.

The API may return a server-hosted cached logo path, such as logos/espn.png, or an absolute URL such as https://example.com/logos/boomerang.png.

function resolveLogo(path) {
  if (!path) return '';
  if (/^https?:\/\//i.test(path)) return path;
  return 'https://dlive.sx/' + path.replace(/^\/+/, '');
}

// Example:
const logo = resolveLogo('logos/espn.png');
// Render with an img element and explicit dimensions.

• Use an img element with fixed width/height or max dimensions.
• Provide a fallback when the image is missing or the host blocks hotlinking.
• SVG, PNG, and JPG may be returned.
• Prefer cached, server-hosted logos when available to reduce third-party requests.

Use the info endpoint to check API metadata and the provider's reported endpoint/authentication information. The exact response fields depend on the API version.

https://dlive.sx/stream/stream-.php
https://dlive.sx/cast/stream-.php
https://dlive.sx/watch/stream-.php
https://dlive.sx/plus/stream-.php
https://dlive.sx/casting/stream-.php
https://dlive.sx/player/stream-.php

Use the channel's channel_id as the ID. Treat it as a string; cast to an integer only if you specifically need numeric sorting.

Swap the folder or channel ID as needed. Add only the iframe permissions the player actually requires. Cross-origin policy, cookies, and embedding restrictions are controlled by the player host and cannot be bypassed from Blogger.

{
  "time": "07:37",
  "event": "Example event title",
  "channels": [
    {"channel_name": "MultiFeed", "channel_id": "277", "logo_url": "logos/multifeed.png"},
    {"channel_name": "BBFeed 1", "channel_id": "261", "logo_url": "logos/bbfeed_1.png"}
  ],
  "channels2": []
}

• Iterate over actual top-level keys rather than splitting category names by a guessed pattern.
• Category names can contain spaces and punctuation.
• Channel IDs are strings, not guaranteed to be numerically sorted.

• Cache schedule and channel responses where the API terms permit it; avoid requesting them repeatedly on every interaction.
• Lazy-load player iframes and create them only after a visitor selects a channel when multiple players are listed.
• Handle HTTP errors, malformed JSON, empty arrays, missing logos, and unavailable player pages.
• Use a fallback image and explicit dimensions to avoid layout shifts.
• Respect the API provider's terms, content rights, and any geographic or embedding restrictions.

• Never commit real keys into a public repository or Blogger template.
• Rotate a key immediately if it is accidentally published.
• Use HTTPS and validate all API data before rendering it.
• Only embed channels and streams you are authorized to distribute.