The Movie Database Support
Support → API Support
Credit endpoint question
posted by thomaxSTAFFMOD on January 20, 2017 at 7:15 AM
Given a list of movies, I'm trying to find which persons constitute a crew and a cast.
To achieve this, I'm fetching movies by genre. Next I fetch credits for each movie (movie/:id/credits). This gives me credits (cast and crew) for each movie. However, each entry in the cast/crew arrays do not include person id. So, I have to grab the credit id and poke the credit/:id endpoint in order to get person id for every single credit. And this is where I'm stuck, because I can't seem to get any result from this last endpoint.
This is Jyn Erso cast credit from Rogue One:
https://api.themoviedb.org/3/credit/5511b37d9251412a88001134?api_key=my-api-key
Response:
{
"status_code": 34,
"status_message": "The resource you requested could not be found."
}
Optimally, there would be a way to get credits included in the response on the first movie-by-genre search. And each credit would not only include the name of the person in question, but the person id. Any chance of making this happen? Any help greatly appreciated
Reply by Travis Bell
on January 20, 2017 at 11:56 AM
Ah yes, I believe there is some problems with the credit end point right now. I have it on my list of things to fix.
But, you're main goal here is actually something I plan on doing TMDb side in the very near of future. Not only if a person in mainly a "crew" or "actor" but also the main job their known for. You'll see this data available in the API soon-ish.
Reply by thomax
on January 24, 2017 at 4:29 AM
Right, thanks for answering! What's the best way to keep tabs on the project so I get the message as soon as this feature is out?
Reply by Travis Bell
on January 24, 2017 at 10:05 AM
For something like this, probably the ticket on Lighthouse. The bigger features tend to get mentioned on the blog.
Reply by tmdbsid
on July 11, 2018 at 8:19 PM
Still not able to get a successful response from the Credit Detail API. Is this still under development?
Thanks!
Reply by Travis Bell
on July 13, 2018 at 6:53 PM
Movie credits are now queryable. Let me know if you see any problems.
The person "known for" field will be added next week.
Cheers.
Reply by tmdbsid
on July 13, 2018 at 9:53 PM
Looking good now Travis. Thanks! The 'known for' field is delivering some data under the Credit Details response. However, it is delivering a just a subset of movies the particular cast or crew member has been involved in, compared to the whole list associated with the person from the Person API. Is there a criteria based on which this subset is being derived from?
Reply by Travis Bell
on July 14, 2018 at 11:39 AM
The
known_forfield you're seeing is on the person object. It's the same data returned by say, person search. That data is built from the "known for" field that you can see on a person. It contains the first 3 items from whatever job that person is known for.What I was referencing above was the API ticket to bring this known for field to the person get details response. The ticket for that is here.
If you want to get a lit of their movies, then yes, you need to make the extra call to /movie_credits.
Reply by Travis Bell
on July 18, 2018 at 12:04 PM
One last update... The person method now includes a
known_for_departmentwhich you can use to know what department to build a persons "known for" data with.Reply by danksky
on February 6, 2019 at 1:12 AM
I've noticed that the credit endpoint isn't serving anything beyond the credit _id and name fields, but on the developer site, it is. What gives?
Reply by Travis Bell
on February 7, 2019 at 12:34 PM
@danksky Can you provide me an example of this?
Movie:
TV Show:
Both seem ok.
Reply by danksky
on February 13, 2019 at 1:06 AM
It turned out to be a logic issue with how I was filtering the response. Sorry to cry wolf!
Reply by Travis Bell
on February 13, 2019 at 1:09 AM
No worries, happy to you sorted it out.