BETA: API & Feeds

Announcements
#47

There’s no plans for exposing channels or guide data in the api right now. It’s focused on your library contents.

#48

Thank you for your reply. The fact that you said "right now" gives me hope for the future. I'm good with that. :grin:

Until then, I'll implement my own script for handling the data from the URL I mentioned. That will keep me busy and out of trouble. :laughing:

3 Likes
#49

Great work on the documentation for the API's!

Is it possible to add the channel number that something was recorded from to the Recordings API for Episodes and Movies?
It currently appears under DVR > Manage > Movies&Shows and Library > Movies&TV Shows.

#50

Sorry for late reply but I've been away.

Submitted: 93b20836-f228-4525-be4d-dc0ee88809fa

I have lots of videos. Running latest beta 2023.02.25.0726

#51

Adding another datapoint for this issue of runtime error (nil pointer) when selecting JSON of all videos.

http://cjynas:8089/api/v1/videos

Selecting JSON output of a specific video group returns the correct JSON and no runtime error.

http://cjynas:8089/api/v1/video_groups/videos-e6e9b8e7c6470c95a347d2b4646357ce1fc911e2a910df1154c803026b6ddbec/videos

2 Likes
#52

Please try this latest build and report back, thanks!

1 Like
#53

Still fails with same runtime error on v2023.02.27.1402.

#54

This is available in the latest pre-release

#55

Are you getting results in the API response? What does the output Response say in the API Explorer?

#56

OK, try this build. I think it will resolve it.

In looking at your diagnostics, you have 2 videos that have no GroupID, therefor, they can't fetch the group they are a part of. I'm not sure how this happened, but it's clearly some kind of bug. Nothing should have a nil GroupID

I'll DM you which videos are the problematic ones.

#57

So, in looking at the problematic videos, it appears that they were missing GroupIDs because they were manual recordings. So we'll look into this more, but at least the problem with the API is resolved. Thanks for reporting it!

#58

Thank You and my scripts thank you :smile:
My curl/jq scripts for Library and Job items are now functional with the new API.

2 Likes
#59

Thanks for having a test case to pitch it against!

2 Likes
#60

As in curl based manual recordings?
I always set .Airing.SeriesID to something like manual/some_id

2 Likes
#61

The issue with runtime error selecting video JSON (no groupID) in the API is working in vers. 2023.02.27.1948

Thanks!

1 Like
#62

When using http://127.0.0.1:8089/api/v1/movies all movie titles contain the release year in parenthesis at the end. Example:

"title": "12 Dates of Christmas (2011)",

The release year is provided separately:

"release_year": 2011,

Could you please remove the release year from the movie title? :pray:

#63

This is how the titles are stored in the library.

2 Likes
#64

Thank you for your reply.
I will format the titles properly in my script.

1 Like
#65

This all looks most excellent, and I'm happy to see it exists.

Having said that - I came looking for an API because I was hoping to update metadata via script; things like changing the Titles and tags and so on. Any ETA for the next step, write access?

#66

We're slowly rolling API support out, starting with read only. We'll make progress towards being able to write to the library eventually. There are plans, there are no timelines.