1 person found this helpful
just a guess- it is not implemented for Jive REST API v3!
The Jive standard content page allows this filtering, but it is using REST API V2...
If you look at the network traffic, you will see these xhr requests.
In general, these limitations suck (there are other areas as well, e.g. for ideas/votes!)!! The format of the calls is not described anywhere (or is it??) and the token is not known to us.
Jive developers, any chance to get results for these endpoints from a custom view tile via osapi calls?
Is this really the case? I see more and more things happening (information not available from the REST API) that won't allow a Jive customer to make his own frontend views / layouts. Certain info is needed to present things in a way we as a customer want.
So we can get a lot out of the REST API but know we as IT people get questions from the business telling us we want to have the list events coming after today!
This is the result when the platform itself does not make use of all the REST endpoints... Jive simple does not know the requirements, so we have to tell them. So good to report this here...
Another workaround would be to get all events from the platform with a batch call (osapi executeBatch) and filter on our own on client side. The performance downgrade depends on the amount of events in the system ...