Feature request: simple JSON view #18
Replies: 4 comments 7 replies
-
Thanks for the suggestion James, I'll take a look. Probably should be precomputed during the daily stats pass and returned via an api subendpoint for the show, something like If you are in a pinch for time, you can grab the stats for the show and compute it yourself (this is what the show stats pages do) using the undocumented show stats endpoint. It's not documented yet since it may change a bit before I'm ready to commit to the api in the public docs. e.g. show stats for podnews daily There are a few optional params if you need to go back in time more than a few months, see the searchParams parsing in the method implementation for what they do. |
Beta Was this translation helpful? Give feedback.
-
Thank you. That's quite the data dump! Goodness. I'd be very happy to help with the headline stats API call if I knew how. My suspicion is that this could be a very cheap API call, and could even be used in directories. |
Beta Was this translation helpful? Give feedback.
-
Once you settle on something I’d like to interface with these stats for PI as well. Good call @jamescridland |
Beta Was this translation helpful? Give feedback.
-
@jamescridland just to clarify, you're looking for those 4 existing show-level metrics (and associated time ranges) at the top of each OP3 show stats page? I've wanted a way to compute an episode-level 30-day download number for a while, since this is the number most folks look at for $$$ purposes, and doesn't bias based on publishing frequency. This number is a bit trickier to compute, since each episode has different numbers (maybe a mean+variance would be better, or simply the latest episode that has reached 30 days). Anyway if I'm running over each show to precompute those existing headline box stats, perhaps I could use this as an excuse to start computing this number as well. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I'm looking for a JSON output that would return four numbers, with four pieces of associated metadata, in a JSON object:
I guess either this could be via an API call, and be a new portion of /worker/routes/api_queries.ts - or it could be just an alternate view of the main show page, in which case the URL could be as simple as /show/55f8007aec094899a02fd44273aa6558/headline.json (with perhaps a last-built date field).
This would enable a quick method of retrieving this headline data, which is lacking (and, selfishly, would allow me to retire a chunk of analytics code that I'm currently running myself).
It strikes me that if this were an alternate view of the main show page, it needn't use an API key and be simpler to produce; and given it's not private data in any way, shouldn't really need an API key to view this information. But I don't know which you'd prefer, given your infrastructure. Which would work better, and is there a way I can help with that?
Beta Was this translation helpful? Give feedback.
All reactions