Post operation on API with token

[avillev]

I'm trying to do a post operation on the API to try to add a movie with the generated token and get this error:

requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://IP:8080/api/users/USERNAME/played/movies

Reads function though. Only that post cannot go though.

Not sure what to do.

[leepeuker]

Can you provide me e.g. a curl http request, so that I can try to reproduce the error?

FYI I am currently pretty buys, I will not be able to look into this and respond in the next few days.

[avillev]

Here is the full thing in curl, in "visible to everyone" mode:

curl -i -s -X POST http://192.168.2.207:8080/api/users/username/played/movies -H "X-Movary-Token:
tokencode" -H "Accept: application/json" -H "Content-Type: application/json" -d '[
{
"movaryId": 11674,
"watchDates": [
{
"watchedAt": "2024-08-08"
}
]
}
]'

HTTP/1.1 403 Forbidden
Server: nginx
Date: Sat, 24 May 2025 05:23:25 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding

I am starting to wonder if the problem isn't that I was too optimistic to think that putting a tmdb id in movaryId would work. And maybe I am getting this error because there is no movie on movary with that id now?

[avillev]

And this discussion tells me that maybe it's not possible at all to add new movies... I wanted to add new movies via API and their tmdbids.

#642

[leepeuker]

And this discussion tells me that maybe it's not possible at all to add new movies... I wanted to add new movies via API and their tmdbids.

Exact, there is currently no endpoint to create movies which do not already exist in Movary.

The movaryId in request payload you posted is the internal id of an existing movie in Movary, not the tmdbId.

I will try to add a API endpoint to add new movies, but I cannot say for sure when I will find the time.

[leepeuker]

Reads function though. Only that post cannot go though.

Oh and please check your Privacy settings on /settings/account/general. If your profile is set to public your token is not checked and you could not get a 403 anyway.

[avillev]

I am in "visible to everyone" mode. So it is not the reason.
If I use "visible to users" ,I cannot even do a read on played movies :'(

[leepeuker]

There was indeed a bug with the API authorization which caused this behavior. This should now be fixed with the 0.65.0 release.