The Endpoint /v1/features replies with { "data": [ { "id": "xxx", "type": "feature", "attributes": {....} }, { "id": "xxx", "type": "feature", ... The "type" field is always "feature&qu...

I can not confirm this. Actually it seems "Bearer" is optional, it can be there, but doesn't have to be (for standard, we are putting it there and it SHOULD be there). Try with different file_id and play a bit and I hope you will confirm this Yes, "Bearer" wasn't the problem as ...

I can not confirm this. Actually it seems "Bearer" is optional, it can be there, but doesn't have to be (for standard, we are putting it there and it SHOULD be there). Try with different file_id and play a bit and I hope you will confirm this Yes, "Bearer" wasn't the problem as ...

Update : I was so confused cuz i got the problem again. Then i downloaded the python api to see if it get the same error and i got no error... I compared the requests made by the python api and my curl requests and i found the difference. The Bearer wasn't the problem. I had to use "https://ww...

Okay i got it working! I had to use --header 'Authorization: <<token>>' \ --header 'Api-Key: <<key>>' \ Yesterday i used the header from the getting started page : -H "Authorization: Bearer <<ACCESS_TOKEN>> which results in a 500 Error for me. If i remove the "Bearer" it works.

Still not working.. I used the spotlight test website. My request : curl --request POST \ --url https://api.opensubtitles.com/api/v1/download \ --header 'Api-Key: <<token>>' \ --header 'Content-Type: application/json' \ --data '{ "file_id": 2391341, "sub_format": "srt",...

Hi, I was just testing the new API a bit and i get the 500 error too. Everything works fine except downloading the actual file. curl --request POST \ --url https://api.opensubtitles.com/api/v1/download \ --header 'Api-Key: <<KEY>> \ --header 'Content-Type: application/json' \ --data '{ "file_id...