@PixeltiniStudio said:
Watch Provider 204 response question
Hi - a couple of items:
I am developing a web-app about ready to alpha test and am testing retrieving watch provider data for movies and tv shows and have had some success in the past couple of days,
however this morning I am receiving a 204 error

This error message is not from the TMDb servers.
We do not have a 204 error.
See the list of possible messages.
https://developer.themoviedb.org/docs/errors

which from documentation sounds like the result was successful but there is not data available.

Nevertheless, post your API Request here.

Problems with API Request

In order for someone to help you with API Request questions,
it is critical that you post here the API Request you are sending to the TMDb server.
Remember to replace your Key with MY_KEY , YOUR_KEY , THE_KEY , or something like that.

Not the programming code/script you used to build the API Request.
But the API Request that is sent to the TMDb server.
Or the API Request you would like to send.

Related, in my API information, I have both an API KEY and a longer API Read Access Token.
The documentation for watch providers mentions use of a Bearer identifier
but I am unclear if this should be set to the API KEY, API Read Access Token or some other value?
Perhaps this is causing the issue?

I am not an expert on this subject. But I believe you should use your TOKEN.
Not your API Key.

Lastly, I'm interested in pricing for commercial use, but a ping to the sales link didn't generate a response yet.
Thanks for the great service!

I can't help you. I don't understand anything about this subject.

Thanks for the response. I am not sure what the issue was with the watch_providers information but it started working again this morning, so perhaps it was a connection issue. Much appreciated.