We’re working with a vendor who reports that the source of this feed: https://events.nyu.edu/live/ical/events/header/All%20Events is rejecting requests from them. It could be timing out, or maybe data is changing as they try and pull it into the application. They suggested that I get in contact with the manager of this data and see if they can review the logs for the vendor’s (Modo) requests.
Hey Rob, thanks for posting – in general we allow all requests to LiveWhale API endpoints (/live/json, /live/ical, /live/rss), and I don’t see anything in particular that would blocking https://events.nyu.edu/live/ical/events/header/All%20Events from your third party source.
It is a pretty large data set – 2.3 MB of upcoming events – and depending on how the 3rd-party application is processing it, perhaps it’s timing out on their end?
One troubleshooting test you could run is using /max/ to cap the number of returned events and see if that works with a smaller data set. For instance, https://events.nyu.edu/live/ical/events/header/All%20Events/max/100
gets you the next 100 upcoming events and is only around 200 kB. If that works with your integration, then you’d know it’s maybe just a file size limitation and you could fiddle to find the sweet spot of a good amount of data to send them, without trying to have them load every upcoming event. Hope this helps!