OpenSubtitles forum

Hi,

The API apparently doesn't support leading zeros, for example:

Code: Select all

https://rest.opensubtitles.org/search/episode-05/imdbid-0455275/season-05

returns a empty response while

Code: Select all

https://rest.opensubtitles.org/search/episode-5/imdbid-0455275/season-5

returns the desired response.

Is this the desired behavior (and should be handled client-side) or this is a bug?

this is working now - following redirects is important:

Code: Select all

curl -L -A 'TemporaryUserAgent' https://rest.opensubtitles.org/search/episode-05/imdbid-0455275/season-03

Hello,

I believe the same problem might be happening to the moviehash field

for example, this request is giving me infinite redirections:
and it redirects to the same request with the wrong hash:

How to search subtitles for movies only? Following query returns zero results curl -A "TemporaryUserAgent" https://rest.opensubtitles.org/search/imdbid-7286456/
while
with language specified it returns results
curl -A "TemporaryUserAgent" https://rest.opensubtitles.org/search/i ... uageid-eng
so is on purpose? Or something is broken for the first query

Why following query doesn't return any results curl -A "TemporaryUserAgent" https://rest.opensubtitles.org/search/imdbid-7286456/

when language is specified it works fine, curl -A "TemporaryUserAgent" https://rest.opensubtitles.org/search/i ... uageid-eng but i would like to get subtitles for all languages

@stephanoumenos - thanks for report, it is now fixed.

@whd - follow redirects (always!) - check redirects and try to make URL according it, so this works ok:

While using the API a user found a subtitle that is a txt file instead of srt. Is it possible using the API to download it as srt or do I need to convert it on my client?

Thanks.

txt is really bad format, we dont offer conversion for this.

I got an email saying authentication will be needed. Does that apply to this api as well? I had asked in the past about authentication for this api but was told it wasn't possible yet.
Also when will this change take place?
Thanks.

this REST API will be abandoned for new REST API we are developing here: https://www.opensubtitles.com/docs/api/html/index.htm

this REST API doesn't need authentication.

this REST API will be disabled later (together with api.opensubtitles.org/xml-rpc) in future (1-2 years in future)

Ok, thank you for the info. Will we be notified a few months before it is removed?

definitely. First let's make run new REST API 100%, then we will send mailing about future plans. So as I wrote, that means at least 1-2 years.

this REST API will be abandoned for new REST API we are developing here: https://www.opensubtitles.com/docs/api/html/index.htm

this REST API doesn't need authentication.

this REST API will be disabled later (together with api.opensubtitles.org/xml-rpc) in future (1-2 years in future)

Hey there ! Nice API I'm trying to provide a golang client for it but I can't seem to manage to login with my account. Do you know if there is any steps I missed?

I just fixed HTTP method OPTIONS, it returns 404 before. Now it is returning 200, so this rest.opensubtitles.org could be used via AJAX calls on other websites.

Can anyone spot what I'm doing wrong with this search?

https://rest.opensubtitles.org/search/e ... uageid-eng

The website returns values, if I use the old api then it works, but on this rest api it doesn't. Other searches work fine with the rest api.

Thanks.

Edit: I noticed the forum was shortening the address so for easy viewing, this is the search /episode-3/query-fear+the+waking+dead/season-6/sublanguageid-eng

it seems ok, the problem is in our index. I can reindex the database and I believe it will start working again properly. Please try again tommorow or let me know it is still not going ok, and I try to reindex.

It is time to test our new API:

https://opensubtitles.stoplight.io/docs ... n_api.json

Thanks.

Is the new api ready for use in a production app?