IPTV API & Xtream Codes Integration Guide for Panel Owners

For developers, custom branding agencies, and advanced resellers, communicating directly with the Xtream Codes API unlocks infinite possibilities—from coding custom automated registration portals to building dedicated streaming apps.

⚙️ API Architecture and Endpoint Mapping

The Xtream Codes API functions using standard HTTP GET/POST queries, returning highly structured JSON objects. Below are the core integration paths for custom software development:

1. Authentication & Subscription Line Payload:

GET http://portal.yourbrand.com:8080/player_api.php?username=CLIENT_USER&password=CLIENT_PASS

Key JSON Response Payload:

{
  "user_info": {
    "username": "client_user",
    "status": "Active",
    "exp_date": "1780158414",
    "max_connections": 1,
    "active_cons": 0
  },
  "server_info": {
    "url": "portal.yourbrand.com",
    "port": "8080"
  }
}

2. Live Channels Category Query:

GET http://portal.yourbrand.com:8080/player_api.php?username=CLIENT_USER&password=CLIENT_PASS&action=get_live_streams

3. Programmatic M3U Fetch Endpoint:

GET http://portal.yourbrand.com:8080/get.php?username=CLIENT_USER&username=CLIENT_USER&password=CLIENT_PASS&action=get_live_streams

⚡ Critical Developer Performance Heuristics

• Active Cache Layer (Redis): Never poll the Xtream Codes API directly for every client connection or playlist load. Store channel categories and server assets in a local cache layer (like Redis or Memcached) with a 12-hour expiration window. Direct, un-cached queries on high-traffic sites will trigger database lockups and crash your server.
• Handling Unix Timestamps: The API returns dates in Unix Epoch format. Convert them in your custom application using new Date(exp_date * 1000) to render readable local date formats for clients.