I have 2 open tickets for this (ticket #316, and #418, which is to replicate the standard movie and tv list objects wherever a movie or TV show is part of the data.

I'm not sure when I'll get to this but it is planned.

Re: reducing the number of requests, are you using append_to_response?

Thanks for the hint to append_to_response. I used it for including videos directly in /movie/. But unfortunately it doesn't colve my problem mentioned above. I tried:

https://api.themoviedb.org/3/person/525/movie_credits?api_key=<12345>&language=de&append_to_response=movies

and

https://api.themoviedb.org/3/person/525/movie_credits?api_key=<12345>&language=de&append_to_response=movie

with no success :(

It would be awesome if the info of a movie (retrieved through /movie/) is included directly in movie_credits.

That's not quite how you use it You can't use it on sub requests, only the primary get info calls. Ie:

https://api.themoviedb.org/3/person/525?api_key=###&language=de&append_to_response=movie_credits

As an example. You're now getting the person details with the credits in a single call. You also chain multiple calls together i.e.:

https://api.themoviedb.org/3/person/525?api_key=###&language=de&append_to_response=movie_credits,external_ids

You can't make movie requests on the person method. The idea of append_to_response is to be able to make sub requests within the same namespace.

Ah, I see.

So is there's currently no chance to achieve what I'm trying :(?

Unfortunately, no.