REST API vs DES endpoints

Version 2

    Referencing:

     

    Query Parameters

     

    The API parameters are modeled after Jive's V3 API.

    • You will need to use the analytics endpoints as they are a separate service.

    You will need to use the filters listed in Using the V2 Jive Data Export Service (Analytics)

    Filters

    The API supports the following filters for limiting results:
    FilterParamsExample
    actionOne or more actions, separated by commas. (See sample JSON response below for action field.)filter=action(View,Create,Update)
    nameOne or more names, separated by commas. (See sample JSON response below for name field.)filter=name(ACTIVITY_CREATE_DOCUMENT)
    userOne or more user search terms.  Compared against username (activity.actor.username in the JSON).filter=user(admin,Administrator)
    typeOne or more content search terms.  Compared against object's type (activity.actionObject.objectType in the JSON).filter=type(blogpost,document)
    placeOne or more destination search terms.  Compared against place name (activity.destination.name in the JSON).filter=place(Cloudalytics)
    matchField followed by one or more search terms.filter=match(activity.actionObject.objectType,Document,Blogpost)
    ltField followed by numeric value — returns events where field's value isless than requested value. (not to be used with timestamp. for less than a time, use before param)filter=lt(activity.actor.objectId,1002)
    gtField followed by numeric value — returns events where field's value isgreater than requested value. (not to be used with timestamp, for greater than a time, use after param)filter=gt(timestamp,1403210186028)
    notNested filter — returns the inverse data set. (New for V2!)filter=not(type(document))filter=not(user(admin,Administrator))
    orNested filter -- returns a filter that is the logical or of the nested filtersfilter=or(type(document),user(admin))

     

    I would also recommend checking out:

    Places in the JC to reference too