We have a feed URL that was working as recently as February 2, but when we’ve tried it recently, it no longer does. Some investigation suggests that it might be due to there being too many tags and groups in the URL, that there’s a limit of 23. However, all of the groups and the tags are necessary for proper functionality. Anyone have an experience like this or insight on how to solve it?
My coworker got a 23 groups-and-tags version of this working without dates.
Hi Rob,
You can usually combine multiple /key/value pairs (when the key is the same) using | separation in the API; does this for example give you what you need? – I’m not sure if there are actually no upcoming events matching those groups + tags or if it might be something else.
Hey Karl, thanks. My coworker produced this URL but the test events he came up with aren’t showing up. What could we try to troubleshoot this? Here’re the events that aren’t showing, attached.
I think the issue is tag/ in the URL: the REST API version of that is tags/ it looks like:
https://events.nyu.edu/live/json/events/tags/nyu-welcome
Thanks so much, Karl. I think we’re getting closer. My coworker tried the link you provided, and we got some events from student-affairs Group but not student-affairs-feed-only, which use a tag. Does that help us in diagnosing this any further?
Hi Rob, hmm, I think I see what you mean – requesting just that group seems to return some results that aren’t being included in the multi-group request.
Something’s definitely going on there, but unfortunately I think we’re about at the limit of what we can diagnose from a browser without digging in to the actual database queries, this might be a good juncture to escalate this to the Request Help Form so our team can take a closer look. 
Thank you! We’ll review internally. Any ideas on why it used to work but doesn’t anymore? Was there a policy change?
Sounds good. The background is, we’ve run into some spam bots taking down calendar sites with exceedingly-long REST requests (spammy /key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value/key/value pair type things) so we’ve added and may continue to tweak system and firewall rules that block REST requests after a certain depth. For instance, in 2.23 we relaxed that rule specifically for embedded widgets, since those can sometimes have super-long REST requests, but the JSON API limit hasn’t been updated to my knowledge since we introduced it in May 2025 with version 2.20.
Thanks for the breakdown. That will be helpful for our team.
