OpenSubtitles forum

should be fixed, please check.

I checked it out, the requests with escaped characters are not failing anymore and the client has no issue following the %20 -> + redirect

perfect, thank you for clarification.

2 more bugs I found:

• Pagination in search subtitles is a bit incorrect, total_pages number is higher than the actual number of pages
  
  Example: https://api.opensubtitles.com/api/v1/su ... id=4154796
  total_pages: 8, total_count: 462, if there are 100 subs per page it should be 5 pages, not 8
• Cached search results appear to be available without an api key?
  For example, try to get https://api.opensubtitles.com/api/v1/su ... 796&page=2 and then try again without an api key a few times, sometimes it will give you the results

2 more bugs I found:

• Pagination in search subtitles is a bit incorrect, total_pages number is higher than the actual number of pages
  
  Example: https://api.opensubtitles.com/api/v1/su ... id=4154796
  total_pages: 8, total_count: 462, if there are 100 subs per page it should be 5 pages, not 8
• Cached search results appear to be available without an api key?
  For example, try to get https://api.opensubtitles.com/api/v1/su ... 796&page=2 and then try again without an api key a few times, sometimes it will give you the results

oh, sorry forgot to reply, the pagination bug was fixed straight away
second bug is not a bug but a feature, once a specific query has been performed, the results are cached a few hours, a cache without validation on the API key, so the behavior is normal

The Endpoint /v1/features replies with The "type" field is always "feature". I know "attributes" contains the field "feature_type" with the real type but this is inconsistent with the models.
It would be easier to parse if the type would be equal to the real type (Movie,TvShow or Episode).

The Endpoint /v1/features replies with

Code: Select all

{ "data": [ { "id": "xxx", "type": "feature", "attributes": {....} }, { "id": "xxx", "type": "feature", ...

The "type" field is always "feature". I know "attributes" contains the field "feature_type" with the real type but this is inconsistent with the models.
It would be easier to parse if the type would be equal to the real type (Movie,TvShow or Episode).

sorry about that, the feature_type was precisely designed for this purpose, we use a dynamic serializer who can return all kind of features (movie,episode.tvshow) so type can't be set.

I know it's annoying, trust me I tried.

Hi. I'm making script for XBMC4Xbox for easier finding and downloading subtitles. And now I have problem which hunts me for almost 2 days. Here is the code from Node.js:



Problem is that I always getting 403 response and I dont know why. API KEY is good because from PostMan with that API KEY everything is working.

hi, we are not node.js developers, soI am afraid we can not help. If it works via postman or curl, then it is working from our side Try to minimize the headers you are sending.

Thanks for your reply. It turns out that GET request takes headers as second argument, while POST request takes it as third argument. Now it's working. I have one more question regarding to TLS/SSL. I think that there is no help, but I hope you dont mind if I ask

On Original Xbox I have Python 2.7.11 with OpenSSL v0.98 which unfortunately does not support newer versions of TLS. When I send HTTP request I get this error: Is there a way for me to bypass this? I can make script for XBMC4Xbox based on old API but in some future that API will be deprecated and probably offline. Currently I fixed problem as my PC is in the middle between Xbox and OpenSubtitles REST API. This is not problem because Node.js is must have because of FFMpeg conversion, but I wanted to make fully working separate Subtitles script for XBMC4Xbox.

understood. for sure you know https://www.packetlabs.net/posts/tls-1- ... er-secure/ but we are not banking institute, so I downgraded minimum TLS from 1.2 to 1.0 - so it can work also on older unable-to-upgrade devices. Let us know.

Thanks. Now it's working. I also noticed one strange behavior. When I pass tmdb_id, season and episode (i.e. 71912, 2, 3) I get empty data. It's The Witcher tv show, and I only noticed this on this tv show, other shows works fine. Same thing happens if I pass imdb_id. However, if I pass query=The Witcher s02e03 I get results.

we are reindexing db, it might be reason. can you send example of imdb_id not working ?

seems it's more an issue with synchronisation at the moment, the series is not on opensubtitles.com, so it won't come out in the API.

too many bugs at the moment, and just got my MacBook back from repair. might take a few days/weeks until errors get fixed