Events (schedule or listings) are a collection of documents of type event in the content instance<\/em> store.<\/p>\n Using either the loop or recursive technique in the Source section above we can retrieve 1000 event documents at a time with the following GET request.<\/p>\n Increment the If you understand the relationships between the document types, we know that events are connected to sources. For each event<\/em> there are The following will retrieve all the event documents of the source with ID “97<\/strong>”<\/p>\n Therefore, if there is a need for it, we can also chunk the retrieval of all event documents by There will be an extra step involved – we will need to gather the list of values for the property we want to chunk the retrieval of events with.<\/strong><\/p>\n The article Getting unique values of a property outlines how to get the list of unique And then we can iterate through each GET https:\/\/<base-url>\/stores-active\/contentinstance\/event\/filter?offset=0&limit=100&api_key=<api-key>\n<\/code><\/pre>\noffset<\/code> value by 1000 (your limit<\/code> value) for each iteration.<\/p>\nChunking by property<\/h4>\n
sourceId<\/code> and source<\/code> properties that identify the source the event is occuring on.<\/p>\nGET: https:\/\/<base-url>\/stores-active\/contentinstance\/event\/filter?filter={\"term\":\"sourceId\",\"value\":\"97\"}&api_key=<api-key>\n<\/code><\/pre>\nExplanation<\/h4>\n
\n\n
\n \nParamenter<\/th>\n description<\/th>\n<\/tr>\n<\/thead>\n \n filter={“term”:”sourceId”,”value”:”97″}<\/td>\n filter the response to documents whose sourceId property has the value of “97”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n sourceId<\/code>, for example.<\/p>\nsourceId<\/code> in the source store. Similarly we can apply the method to the event document against the sourceId<\/code> property.<\/p>\nsourceId<\/code> and submit the above request by replacing “97” with current sourceId<\/code> in each iteration.<\/p>\n