Xtream api proxy - response from player_api.php causing an error in iptv-proxy #19
Replies: 7 comments 2 replies
-
I have pushed the changes. One of the biggest Problems i have is, that i couldnt find a schema desctiption for the xtream api json format. |
Beta Was this translation helpful? Give feedback.
-
superb - iil test and report back |
Beta Was this translation helpful? Give feedback.
-
thanks that call is working now 👍 however the call to xmltv.php is failing now - is that a call that mp3-filter should handle? iptv-proxy
m3u-filter
|
Beta Was this translation helpful? Give feedback.
-
xml..php is on my todo list. |
Beta Was this translation helpful? Give feedback.
-
one more question... apologies if ive missed the docs for this but im not clear how to build the |
Beta Was this translation helpful? Give feedback.
-
the frontend is build with nodejs. You need nodejs, then install yarn. Inside the frontemd folder type
The |
Beta Was this translation helpful? Give feedback.
-
there is a Script in the bin folder. |
Beta Was this translation helpful? Give feedback.
-
@euzu i wanted to discuss this here rather than raise an issue as im not sure if this is problem with m3u-filter of not.
Im progressing implementing m3u-filter with iptv-proxy. it now works well with a URL playlist however im having some issues with Xtream
when iptv-proxy call the api-proxy for m3u-filter i get an error in iptv proxy from the response from m3u-filter
This seems to be the result of this response
The responser i get from my iptv provider directly is this
the only difference seems to be that some INTs are presented as strings in the response from my IPTV provider. i cant find any doumentation on the types of the response payload for the api call but just wanted to check whether this all looked correct to you? thx
Beta Was this translation helpful? Give feedback.
All reactions