Get an incremental stream of changes to Member Values

Monitor any incremental changes to Member Values in your community.

This is useful in cases where an incremental extraction of information is required. This request is more complex than attempting a periodic bulk mode request, but allows for more efficient and low latency ongoing extraction.

API request format

GET /membervalues?memberDataSetType=Live&q="lastUpdateDate>="{datetime}""&membervariableid={comma-separated list of member variable IDs}&fields=id,memberid,memberVariableId,memberVariableName,memberVariableType,memberVariableValue,lastUpdateDate,effectiveDate&sort=effectiveDate,lastUpdateDate&limit=100

Content Control

The parameters used in the request are described below:

Parameter	Description
memberDataSetType=Live	Returns live data. To return test data, use memberDataSetType=Test.
q="lastUpdateDate>="{datetime}""	Returns Member Values that have been created or changed since {datetime}. This relies on the consumer keeping track of the maximum lastUpdateDate found in previous incremental pulls. Note: Do not filter your data on effectiveDate. It is likely that the latest data will be added; however, the service does support recording of Member Values with an effectiveDate in the past (and not equal to the lastUpdateDate). For more information, see Content control. Tip: If the query string parameter q does not work, encode the URL. For more information, see HTML URL Encoding Reference.
membervariableid={comma-separated list of member variable IDs}	Returns Member Values for Member Variables whose IDs are included in the comma-separated list.
fields=id,memberid,memberVariableId,memberVariableName, memberVariableType,memberVariableValue,lastUpdateDate,effectiveDate	Limits the number of fields returned per item, which increases performance.
sort=effectiveDate,lastUpdateDate	Sorts results by effectiveDate first (ascending order, most recent first), and then by lastUpdateDate (ascending order, most recent first) whenever two or more effectiveDate values are equal. This ordering is likely more useful.
limit=1000	Setting the maximum for limit (1000) will reduce the number of round trips required to page through large return sets.

For more information, see Content control.

Parent topic: Use an email address to retrieve a member ID