{"id":728,"date":"2026-10-17T12:02:13","date_gmt":"2026-10-17T12:02:13","guid":{"rendered":"https:\/\/wolftv.org\/iptv-plex-jellyfin-live-tv-media-server-guide-2026\/"},"modified":"2026-10-19T15:52:24","modified_gmt":"2026-10-19T15:52:24","slug":"iptv-plex-jellyfin-live-tv-media-server-guide-2026","status":"publish","type":"post","link":"https:\/\/wolftv.org\/fr\/iptv-plex-jellyfin-live-tv-media-server-guide-2026\/","title":{"rendered":"IPTV in Plex &amp; Jellyfin 2026: The Complete Live TV Media Server Guide"},"content":{"rendered":"<p>Most people who cut the cord assume they are done once their new IPTV subscription is paid for and their player app is installed. In practice, that is only the first half of the job. The second half \u2014 and the part that actually determines whether you get buffer-free 4K on a Sunday afternoon or a spinning circle in the middle of a fourth quarter \u2014 is how well your <strong>Plex or Jellyfin server is connected to your live TV source<\/strong>. That is where IPTV meets the home media server.<\/p>\n<p>This guide is a practical, technical walkthrough for anyone who already runs Plex or Jellyfin and wants live channels, sports, and scheduled recordings sitting in the same interface as their movie library. We will cover how Plex and Jellyfin actually ingest live TV, how to prepare an M3U playlist and XMLTV guide so channels look right, what hardware and network choices keep playback smooth, and how to diagnose the problems that make live TV on a media server feel worse than a cheap streaming stick. Along the way we will point out where a managed service such as <a href=\"https:\/\/wolftv.org\/fr\/\">WolfTV<\/a> removes most of the manual work.<\/p>\n<h2>Why put IPTV inside Plex or Jellyfin at all?<\/h2>\n<p>A dedicated IPTV player like TiviMate or IPTV Smarters is purpose-built for channel surfing: fast zapping, a cable-style guide, and simple recording. A media server is a different kind of tool. It is built around a library, a database, and a transcoder. Bringing live TV into that environment buys you four things a player app cannot easily match.<\/p>\n<ul>\n<li><strong>One interface for everything.<\/strong> Your live channels, your DVR recordings, and your on-demand library appear in the same app on the same TV, with the same remote.<\/li>\n<li><strong>Real DVR infrastructure.<\/strong> Plex and Jellyfin record to your own disks, in your own format, with no cloud expiry dates or provider-side retention limits. Recordings behave like any other library item afterwards.<\/li>\n<li><strong>Server-side transcoding.<\/strong> A single stream can be turned into whatever your client needs \u2014 direct play on a capable TV, a lower bitrate for a phone on mobile data, or a burned-in subtitle track \u2014 instead of asking the IPTV provider to deliver five different versions.<\/li>\n<li><strong>Multi-user, multi-room sharing.<\/strong> User accounts, watch state, parental restrictions, and remote access are already solved problems in a media server. Adding live TV inherits all of it.<\/li>\n<\/ul>\n<p>The trade-off is complexity: a media server&#8217;s live TV pipeline has more moving parts than a player app, so each part needs to be set up correctly. That is the rest of this article.<\/p>\n<h2>How Plex and Jellyfin actually handle live TV<\/h2>\n<p>Both platforms use the same conceptual model, borrowed from the broadcast world. Understanding it makes every later troubleshooting step obvious instead of mysterious.<\/p>\n<h3>Three ingredients: tuner, guide, client<\/h3>\n<p>Plex calls the components a <em>tuner<\/em>, an <em>EPG<\/em> (electronic program guide), and a client. Jellyfin uses the same idea under different names: a <em>Live TV source<\/em>, a <em>guide data provider<\/em>, and a playback client.<\/p>\n<ul>\n<li><strong>The source<\/strong> is where the channel stream comes from. With an over-the-air antenna it is a physical tuner such as an HDHomeRun. With IPTV it is a playlist URL plus, usually, an XMLTV guide URL.<\/li>\n<li><strong>The guide<\/strong> maps channel identifiers to program names, descriptions, start times, and durations. Without guide data you get a list of numbers and no ability to schedule recordings.<\/li>\n<li><strong>The client<\/strong> is the app on your TV, phone, or browser. The server decides what to send it: a direct stream, a remux, or a full transcode.<\/li>\n<\/ul>\n<p>Nearly every live TV failure you will ever see on a media server is a failure in exactly one of these three layers. When something breaks, the first question is always: is the problem the source, the guide, or playback?<\/p>\n<h3>What the server does that a player app does not<\/h3>\n<p>When a client asks Plex or Jellyfin to play a channel, the server probes the incoming stream, inspects its codecs and container, checks what the client can decode natively, and then chooses the cheapest path. If the client supports the codec, the bytes are passed through untouched \u2014 the best possible outcome. If not, the server transcodes in real time, which costs CPU or GPU and introduces a small startup delay.<\/p>\n<p>This is fundamentally different from TiviMate or IPTV Smarters, which decode locally on the device and have no server in the middle. A media server adds quality-of-experience features at the cost of an extra hop and a transcoding budget you must respect. The relevant background on how that encoding and packaging works is worth reading if you want the deeper technical picture: <a href=\"https:\/\/en.wikipedia.org\/wiki\/Adaptive_bitrate_streaming\" target=\"_blank\" rel=\"noopener noreferrer\">adaptive bitrate streaming<\/a>, <a href=\"https:\/\/en.wikipedia.org\/wiki\/MPEG-DASH\" target=\"_blank\" rel=\"noopener noreferrer\">MPEG-DASH<\/a>, et le <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8216\" target=\"_blank\" rel=\"noopener noreferrer\">HLS specification (RFC 8216)<\/a>.<\/p>\n<h2>Before you start: the prerequisites most guides skip<\/h2>\n<p>People routinely install the live TV feature, paste a URL, and then wonder why nothing works. The failure is usually one of the items below, so check them first.<\/p>\n<ul>\n<li><strong>Plex Pass.<\/strong> Live TV and DVR in Plex require an active Plex Pass subscription. Jellyfin has no equivalent paywall for live TV.<\/li>\n<li><strong>A supported playlist format.<\/strong> Both platforms accept M3U playlists. Xtream Codes\u2013style providers also expose M3U URLs derived from your username, password, and server host.<\/li>\n<li><strong>Guide data.<\/strong> An XMLTV URL is strongly preferred. Without it, Plex and Jellyfin can still tune channels, but scheduling recordings becomes guesswork.<\/li>\n<li><strong>A wired server.<\/strong> Ethernet on the server is not optional if you want stable 4K. Wi-Fi on a server that is simultaneously reading a playlist, writing a recording, and transcoding is where most &#8220;IPTV is buffering&#8221; complaints actually originate.<\/li>\n<li><strong>Disk space for recordings.<\/strong> A single hour of 1080p broadcast can be one to three gigabytes before transcoding. Twenty series passes can fill a small drive in weeks.<\/li>\n<\/ul>\n<h2>Step-by-step: adding an IPTV playlist to Jellyfin<\/h2>\n<p>Jellyfin is the cleaner starting point because it exposes the whole pipeline in one settings page. The order matters.<\/p>\n<ol>\n<li><strong>Confirm the playlist URL works in isolation.<\/strong> Open the M3U URL in a browser or run a quick <code>curl<\/code> against it. You should see <code>#EXTM3U<\/code> followed by channel entries. If the URL redirects to a login page or returns HTML, the credentials are wrong and no amount of configuration inside Jellyfin will help.<\/li>\n<li><strong>Add the tuner.<\/strong> Allez \u00e0 <em>Dashboard \u2192 Live TV<\/em> and add a tuner of type <em>M3U Tuner<\/em>. Paste the playlist URL. Set the &#8220;number of simultaneous connections&#8221; to match your subscription&#8217;s stream limit \u2014 not higher.<\/li>\n<li><strong>Add the guide.<\/strong> Add a guide provider of type <em>XMLTV<\/em> and paste the XMLTV URL. Assign the tuner to the guide and let Jellyfin map channels. Mapping is usually automatic when the playlist and the guide use matching <code>tvg-id<\/code> values.<\/li>\n<li><strong>Set the refresh interval.<\/strong> Guide refreshes should happen once or twice a day, ideally in the early morning. Refreshing every fifteen minutes hammers the provider&#8217;s server and can get your credentials rate-limited.<\/li>\n<li><strong>Enable DVR.<\/strong> Set a recording path on a drive with real capacity, and choose a recording format. A remux to MKV keeps original quality with no CPU cost; a transcode is only worth it if disk space is tight.<\/li>\n<li><strong>Test one channel before adding twenty favourites.<\/strong> Tune a single 1080p channel from a client, watch for two minutes, then check the Jellyfin log for the chosen playback method.<\/li>\n<\/ol>\n<p>For Plex, the flow is the same in spirit: <em>Settings \u2192 Live TV &amp; DVR \u2192 Set Up Plex DVR<\/em>, choose the &#8220;M3U\/XMLTV&#8221; option rather than an HDHomeRun device, supply both URLs, then map channels and create the DVR. Plex is more opinionated about channel numbering and is less forgiving of malformed playlists, so a clean list helps.<\/p>\n<h2>Cleaning up the playlist and guide (the highest-leverage step)<\/h2>\n<p>A raw IPTV playlist from a provider is rarely tidy. It will have thousands of entries, regional duplicates, channels with no guide data, and names in inconsistent formats. The media server does exactly what the playlist says, so a messy list produces a messy library.<\/p>\n<h3>Channel identifiers are the whole game<\/h3>\n<p>The link between a playlist entry and a guide entry is the <code>tvg-id<\/code> attribute. If your playlist says <code>tvg-id=\"BBCOne.uk\"<\/code> and your guide uses <code>BBCOne.uk<\/code> as well, mapping is instant. One character of difference and Jellyfin sees an unmapped channel.<\/p>\n<ul>\n<li>Extract the playlist and inspect a handful of <code>#EXTINF<\/code> lines to confirm <code>tvg-id<\/code>, <code>tvg-name<\/code>, <code>tvg-logo<\/code>, et <code>group-title<\/code> are populated.<\/li>\n<li>In Jellyfin, use the channel mapping page to correct mismatches and to hide channels you will never watch. Hiding is not cosmetic \u2014 it reduces guide refresh time and database size substantially.<\/li>\n<li>Prefer a curated subset. A 40-channel list with perfect guide data beats a 12,000-channel list where half the entries are dead. If your provider offers regional or language-filtered playlist URLs, use them.<\/li>\n<\/ul>\n<p>This is where a managed service saves the most time. A provider that ships a clean, deduplicated playlist with consistent <code>tvg-id<\/code> mapping and a matching XMLTV feed turns a two-hour organising project into a five-minute setup. WolfTV, for example, publishes device-specific setup guides for exactly this reason \u2014 the IPTV playlist is meant to be dropped straight into a player or a media server without editing. If you want the broader context on how these lists are structured, the <a href=\"https:\/\/wolftv.org\/fr\/what-is-iptv-and-how-does-it-work-beginners-step-by-step-guide\/\">beginner&#8217;s guide to how IPTV works<\/a> covers the mechanics.<\/p>\n<h2>Choose the right codecs to avoid transcoding<\/h2>\n<p>The single biggest performance decision you make is whether your clients can direct play your channels. Direct play means the server only forwards bytes. Transcoding means the server decodes, re-encodes, and repackages in real time \u2014 and suddenly your CPU matters more than your internet connection.<\/p>\n<ul>\n<li><strong>H.264 \/ AVC<\/strong> remains the most compatible video codec. Almost every TV, phone, and stick decodes it in hardware. If your provider offers an H.264 stream option, take it.<\/li>\n<li><strong>HEVC \/ H.265<\/strong> halves the bitrate for the same quality but is only universally supported on newer hardware. Good for 4K, risky for older Fire TV devices and budget Android boxes. See the <a href=\"https:\/\/en.wikipedia.org\/wiki\/H.265\" target=\"_blank\" rel=\"noopener noreferrer\">HEVC overview<\/a> for the compatibility details.<\/li>\n<li><strong>Audio is the silent killer.<\/strong> A stream with AC-3 or E-AC-3 audio will trigger an audio transcode on devices that only decode stereo. Check the log; &#8220;direct stream video, transcode audio&#8221; is a common and cheap fix pattern.<\/li>\n<li><strong>Container matters too.<\/strong> MPEG-TS is universal for live streams; Plex and Jellyfin handle remuxing it into HLS for network clients automatically.<\/li>\n<\/ul>\n<p>If a channel insists on transcoding, the answer is usually a cheap GPU with hardware encoding rather than a bigger CPU \u2014 Intel Quick Sync on a modern Celeron or Core i3 handles several simultaneous 1080p transcodes comfortably and does it at a fraction of the power draw.<\/p>\n<h2>Network and hardware: where live TV actually breaks<\/h2>\n<p>Media-server live TV is more network-sensitive than file playback, because there is no read-ahead buffer worth mentioning. A stream arrives in near real time and the server must deliver it to the client in near real time as well.<\/p>\n<ul>\n<li><strong>Wire the server.<\/strong> Gigabit Ethernet between the server and the router. This alone resolves a large share of &#8220;it buffers at 4K but not at 720p&#8221; reports.<\/li>\n<li><strong>Wire the TV if you can.<\/strong> Many TVs ship with 100 Mbps Ethernet and mediocre Wi-Fi; if Wi-Fi is unavoidable, use the 5 GHz or 6 GHz band and keep the access point in line of sight.<\/li>\n<li><strong>Do not put the server on a VPN tunnel by default.<\/strong> A VPN on the server adds latency and jitter to every byte and prevents local clients from reaching it. Put the VPN in front of the <em>IPTV fetch<\/em> only if you have a specific reason, and understand the trade-off before doing so.<\/li>\n<li><strong>Mind the transcoder&#8217;s storage.<\/strong> Transcode scratch space should be on a fast SSD. A slow disk on the transcode path produces stutter that looks exactly like a network problem.<\/li>\n<li><strong>Surveillez la limite de connexion.<\/strong> Si votre abonnement autorise deux flux simultan\u00e9s et que l&#039;enregistreur num\u00e9rique enregistre deux \u00e9missions, tout spectateur suppl\u00e9mentaire ne pourra pas se connecter. R\u00e9servez une connexion pour l&#039;enregistreur num\u00e9rique les soirs d&#039;\u00e9v\u00e9nements.<\/li>\n<\/ul>\n<p>Si vous h\u00e9sitez encore sur le mat\u00e9riel, les diff\u00e9rences entre un Fire TV Stick, une NVIDIA Shield et un PC compact sont r\u00e9ellement importantes pour les clients de serveurs multim\u00e9dias. Notre comparatif de <a href=\"https:\/\/wolftv.org\/fr\/appareils\/iptv-fire-stick\/\">appareils IPTV<\/a> Ce guide d\u00e9crit quels bo\u00eetiers lisent directement et de mani\u00e8re fiable le codec HEVC et lesquels utilisent discr\u00e8tement le d\u00e9codage logiciel.<\/p>\n<h2>Diagnostiquer les probl\u00e8mes sans deviner<\/h2>\n<p>Pour r\u00e9soudre rapidement un probl\u00e8me de diffusion TV en direct sur un serveur multim\u00e9dia, il est conseill\u00e9 d&#039;arr\u00eater de modifier les param\u00e8tres au hasard et de consulter le journal. Les deux plateformes y consignent les d\u00e9cisions de lecture exactes qu&#039;elles ont prises.<\/p>\n<h3>Un ordre de triage simple<\/h3>\n<ol>\n<li><strong>L&#039;URL fonctionne-t-elle en dehors du serveur multim\u00e9dia\u00a0?<\/strong> Testez-le avec un lecteur de bureau ou <code>curl<\/code>. Si cela \u00e9choue, le probl\u00e8me vient de la source ou de vos identifiants.<\/li>\n<li><strong>La cha\u00eene se syntonise mais n&#039;affiche aucune donn\u00e9e de guide\u00a0?<\/strong> Il s&#039;agit d&#039;un probl\u00e8me de mappage, et non d&#039;un probl\u00e8me de flux. Corriger <code>tvg-id<\/code> d&#039;abord.<\/li>\n<li><strong>Est-ce que le son se lance pendant quelques secondes puis se bloque ?<\/strong> Il s&#039;agit g\u00e9n\u00e9ralement d&#039;un probl\u00e8me de bande passante ou de limite de connexion du fournisseur d&#039;acc\u00e8s, parfois d&#039;une image cl\u00e9 manquante. Consultez le journal du serveur pour d\u00e9tecter les erreurs HTTP sur les segments.<\/li>\n<li><strong>L&#039;image saccade-t-elle alors que le son est correct\u00a0?<\/strong> Il s&#039;agit presque toujours d&#039;un goulot d&#039;\u00e9tranglement au niveau du transcodage. Surveillez les pertes d&#039;images et la saturation du processeur ou de la carte graphique.<\/li>\n<li><strong>Cela fonctionne-t-il chez un client et pas chez un autre\u00a0?<\/strong> Prise en charge du codec ou du conteneur c\u00f4t\u00e9 client. Comparez les deux entr\u00e9es de journal c\u00f4te \u00e0 c\u00f4te.<\/li>\n<\/ol>\n<p>Les outils sont utiles ici. <a href=\"https:\/\/www.wireshark.org\/\" target=\"_blank\" rel=\"noopener noreferrer\">Wireshark<\/a> indiquera si les segments arrivent lentement ou pas du tout, et le <a href=\"https:\/\/nvd.nist.gov\/\" target=\"_blank\" rel=\"noopener noreferrer\">Base de donn\u00e9es de vuln\u00e9rabilit\u00e9s NVD<\/a> C&#039;est le bon endroit pour v\u00e9rifier si une application de lecteur ou un plugin serveur que vous avez install\u00e9 pr\u00e9sente un probl\u00e8me connu qui justifie une correction imm\u00e9diate.<\/p>\n<h2>S\u00e9curit\u00e9 et hygi\u00e8ne des sources<\/h2>\n<p>Ajouter une playlist tierce \u00e0 un serveur h\u00e9bergeant \u00e9galement votre biblioth\u00e8que multim\u00e9dia personnelle est une d\u00e9cision qui repose sur la confiance, et non sur une simple configuration. Quelques bonnes habitudes permettent de prendre cette d\u00e9cision en toute s\u00e9curit\u00e9.<\/p>\n<ul>\n<li><strong>Faites appel \u00e0 un prestataire jouissant d&#039;une v\u00e9ritable r\u00e9putation et d&#039;une situation juridique solide.<\/strong> Les services l\u00e9gitimes obtiennent une licence pour les cha\u00eenes qu&#039;ils distribuent. Si un service vend des milliers de cha\u00eenes premium pour le prix d&#039;un caf\u00e9, il n&#039;est pas agr\u00e9\u00e9 et vous en assumez les risques.<\/li>\n<li><strong>Ne r\u00e9utilisez jamais un mot de passe important.<\/strong> Les identifiants IPTV se retrouvent dans les URL, les fichiers de configuration et les captures d&#039;\u00e9cran. Consid\u00e9rez-les comme jetables et uniques.<\/li>\n<li><strong>N\u2019installez pas de fichiers APK provenant de miroirs al\u00e9atoires.<\/strong> Sur Fire OS en particulier, l&#039;installation de fichiers hors du syst\u00e8me d&#039;exploitation (sideloading) est devenue plus restreinte et plus risqu\u00e9e ; si vous devez absolument effectuer une installation hors du syst\u00e8me d&#039;exploitation, v\u00e9rifiez la source et la somme de contr\u00f4le.<\/li>\n<li><strong>Maintenez le serveur \u00e0 jour.<\/strong> Jellyfin et Plex publient tous deux des avis de s\u00e9curit\u00e9. Installez la version actuelle et consultez le journal des modifications.<\/li>\n<li><strong>Isolez-vous en cas de doute.<\/strong> L&#039;ex\u00e9cution d&#039;un client inconnu sur un VLAN distinct ou un r\u00e9seau invit\u00e9 limite l&#039;\u00e9tendue des d\u00e9g\u00e2ts qu&#039;une application malveillante peut causer.<\/li>\n<\/ul>\n<p>Pour conna\u00eetre le cadre l\u00e9gal et savoir comment distinguer un service l\u00e9gal d&#039;un site de piratage, consultez notre guide. <a href=\"https:\/\/wolftv.org\/fr\/iptv-not-working-2026-fixes-firestick-tivimate-smart-tv\/\">L\u00e9galit\u00e9 et s\u00e9curit\u00e9 du streaming IPTV<\/a> passe en revue les distinctions en d\u00e9tail.<\/p>\n<h2>Quand un serveur multim\u00e9dia n&#039;est pas l&#039;outil appropri\u00e9<\/h2>\n<p>Un conseil sinc\u00e8re\u00a0: Plex et Jellyfin ne sont pas forc\u00e9ment meilleurs qu&#039;une application de lecture. Optez pour un serveur multim\u00e9dia si vous souhaitez conserver vos enregistrements dans votre biblioth\u00e8que, g\u00e9rer plusieurs comptes utilisateurs et effectuer le transcodage pour les t\u00e9l\u00e9phones et le visionnage \u00e0 distance. Choisissez TiviMate, IPTV Smarters ou un lecteur similaire si vous zappez principalement, recherchez la rapidit\u00e9 de changement de cha\u00eene et ne souhaitez pas g\u00e9rer de serveur.<\/p>\n<p>Une configuration hybride est souvent id\u00e9ale\u00a0: conservez le serveur multim\u00e9dia pour l\u2019enregistrement et le visionnage sur t\u00e9l\u00e9phones et tablettes, et un lecteur d\u00e9di\u00e9 sur le t\u00e9l\u00e9viseur principal pour les \u00e9v\u00e9nements sportifs en direct o\u00f9 un changement de cha\u00eene en une seconde est crucial. Les deux appareils peuvent utiliser la m\u00eame liste de lecture et le m\u00eame guide des programmes, et tant que vous respectez votre limite de connexions simultan\u00e9es, ils coexistent sans probl\u00e8me.<\/p>\n<h2>La version courte<\/h2>\n<ul>\n<li>La t\u00e9l\u00e9vision en direct sur Plex ou Jellyfin fonctionne avec trois niveaux\u00a0: source, guide des programmes et client. Il faut diagnostiquer le probl\u00e8me au niveau du probl\u00e8me, et non le sympt\u00f4me.<\/li>\n<li>Une playlist M3U propre avec des \u00e9l\u00e9ments corrects <code>tvg-id<\/code> Des valeurs et un guide XMLTV correspondant valent plus que n&#039;importe quel r\u00e9glage.<\/li>\n<li>La lecture directe est toujours pr\u00e9f\u00e9rable au transcodage\u00a0: choisissez H.264 pour la compatibilit\u00e9, HEVC pour la bande passante, et observez le codec audio.<\/li>\n<li>C\u00e2blez le serveur, r\u00e9servez une connexion pour le DVR et placez les donn\u00e9es de travail de transcodage sur un SSD.<\/li>\n<li>Consultez le journal du serveur. Il vous indiquera pr\u00e9cis\u00e9ment quelle d\u00e9cision a \u00e9t\u00e9 prise et pourquoi.<\/li>\n<\/ul>\n<p>Ma\u00eetrisez ces cinq points et la t\u00e9l\u00e9vision en direct sur un serveur multim\u00e9dia deviendra bien meilleure que le d\u00e9codeur qu&#039;elle a remplac\u00e9\u00a0: vos cha\u00eenes, vos enregistrements, votre biblioth\u00e8que, sur tous les \u00e9crans de la maison, sans frais de location. Commencez par une source offrant une liste de lecture claire et un guide des programmes fiable, testez avec une cha\u00eene, puis \u00e9largissez votre choix\u00a0: voil\u00e0 la m\u00e9thode.<\/p>","protected":false},"excerpt":{"rendered":"<p>How to add IPTV to Plex and Jellyfin in 2026: M3U playlists, XMLTV guide mapping, codec choices that avoid transcoding, DVR setup, and fixes for buffering on a media server.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[39,33,36,58,8,46,7,64,35,143,13,48,57,142,30,10,9,65],"class_list":["post-728","post","type-post","status-publish","format-standard","hentry","category-blog","tag-4k-streaming","tag-android-tv","tag-epg","tag-fifa-world-cup-2026","tag-firestick","tag-google-tv","tag-iptv","tag-iptv-player","tag-iptv-smarters","tag-jellyfin-live-tv","tag-live-tv","tag-m3u","tag-multi-room-streaming","tag-plex-iptv","tag-smart-tv","tag-streaming","tag-tivimate","tag-tivimate-4-0"],"_links":{"self":[{"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/posts\/728","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/comments?post=728"}],"version-history":[{"count":1,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/posts\/728\/revisions"}],"predecessor-version":[{"id":735,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/posts\/728\/revisions\/735"}],"wp:attachment":[{"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/media?parent=728"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/categories?post=728"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wolftv.org\/fr\/wp-json\/wp\/v2\/tags?post=728"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}