This is no longer working due to Just watch API changes

[voodooenglishman]

I believe this no longer works could be wrong as I can't find an older version of the justwatch API documentation but I believe its changed since the last update to this

Tried running one of my usual scripts and was given errors down to this API in my code

Was getting 404 errors

https://apis.justwatch.com/docs/api/

Looking at the current API and the code from this it seems the URLs are no longer pointing correctly

Example being the new base URL which is "https://apis.justwatch.com/contentpartner/v2/content" which is different from the one given within this API

Thank you

[NRaabjerg]

I am experiencing the same issue. I believe JustWatch have closed public API access. I will try to look further into it, but hopefully someone will be able to get around it at some point.

[dseomn]

I'm getting 404s trying to access content and search pages, but https://apis.justwatch.com/content/locales/state and https://apis.justwatch.com/content/providers/locale/en_US are still working for me. Over the past few days I also noticed missing seasons fields in some TV show pages, which all got fixed eventually. Maybe JustWatch is just doing some sort of migration and it's not going smoothly for this API?

But if the current API is going away, lufinkey/node-justwatch-api#17 mentions a graphql API that might work instead?

[byte4geek]

Same for me

[anemochore]

Same here. I searched and found reddit post and then I was able to get it work again. (changed whole payload)

[DiegoFleitas]

Idem, GraphQL might be the only viable option now

[dseomn]

In case it helps anyone, here's some code I got working using the GraphQL API. For what it's worth, the new API feels significantly more powerful than the old API in some ways, though it also wasn't a trivial migration to the new API.

https://github.com/dseomn/rock-paper-sand/blob/70bf3542f65b6a3ca92f0784e64bcc29476a393d/rock_paper_sand/justwatch.py#L64

[anemochore]

Well, I suspect if my TamperMonkey script will help, but this is my code. (Somehow reverse engineered with help of reddit post previously mentioned) My scenario is searching by title and then getting original title, year, type, imdb rating, etc. https://github.com/anemochore/imdbOnWatcha/blob/master/utils.js#L80

[dseomn]

Edit: sorry for the noise, this was an issue with my code, not with the API. I was caching all "successful" HTTP requests, including ones that return JSON with an errors key. So it looked like the API kept returning the error below, but it actually just returned it once and my code cached that.

I just started getting errors like the below from the graphql API. Note that the HTTP response code was 200 (or some other non-error code), and the mention of 429 is in the response body. Is anybody else seeing something like this with the new API?

{'errors': [{'message': 'rpc error: code = Unknown desc = getting offers: GetTitleOffers: reading from source: error response received from Elasticsearch: 429 Too Many Requests', 'path': ['urlV2', 'node', 'seasons', 0, 'episodes', 5, 'offers'], 'extensions': {'code': 'INTERNAL_ERROR'}}, {'message': 'rpc error: code = Unknown desc = getting offers: GetTitleOffers: reading from source: error response received from Elasticsearch: 429 Too Many Requests', 'path': ['urlV2', 'node', 'seasons', 1, 'episodes', 9, 'offers'], 'extensions': {'code': 'INTERNAL_ERROR'}}], 'data': None}

[anemochore]

@dseomn Error message says 'Too Many Requests.' Maybe you are requesting too many. In my case, no such errors occured.

[dseomn]

See the "Edit: ..." text I added to that comment. It was just a transient issue, probably from too many requests to their backend, not too many requests from me. The fix was easy: dseomn/rock-paper-sand@692e63c

[DiegoFleitas]

Thanks for sharing that demo, @dseomn! By the way, for anyone else tinkering with this, I think I encountered a quirk regarding the newline characters used in GraphQL queries: there's a different behavior when using \r\n versus \n. So, if you come across any strange behavior, checking the newline characters might be a good place to start. I believe the API may have cached an error response for a seemingly correct request. The errors ceased when I switched to using \r\n as the newline character in my queries.

[DanielSouzaBertoldi]

After reading the code of both projects listed here and the reddit post, I'm still not sure on how to fetch info of a media by passing along only its ID + objectType. Checking out the /graphql requests in the JustWatch site I can only find operations for GetTitlePopularityRank and GetSimilarTitles 🤔 has anyone figured out what's the query for this?

[dseomn]

https://github.com/dseomn/rock-paper-sand/blob/9a26853a0c7a5c68a536b30e69e2cc16c5e4f572/rock_paper_sand/justwatch.py#L233 looks up details by node ID, which is basically just object type + object ID. E.g., object type "SHOW" and object ID "42" is node ID "ts42". I think movies are "tm...", seasons are "tss..." and episodes are "tse...", but I didn't double check that.

[DanielSouzaBertoldi]

@dseomn nice, thanks for the quick reply! Instead of just asking for the offers data I also added the following to the Movie fragment just to test it out:

fragment Movie on Movie {
    __typename
    id
    content(country: $country, language: $language) {
        fullPath
        title
        originalReleaseYear
        originalTitle
        scoring {
        imdbScore
        imdbVotes
        __typename
        }
        externalIds {
        imdbId
        __typename
        }
        __typename
    }
    offers(country: $country, platform: WEB) {
        monetizationType
        availableToTime
        availableFromTime
        package {
            clearName
            technicalName
        }
    }
}

And it worked, nice. The worst part is figuring out what field name to use for a given data.