Before assigning a collection of Member Values, check to see if a member exists to:
- Improve the performance of the API when working with large batches of information
- Prevent confusion if the member's email has changed
Tip: The same is true for Member Variable Values, where
specification by ID will also perform slightly better and not be prone to
problems when the name of a Member Variable is changed.
Example: POST /membervalues
[
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": "Chicago"
},
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": "1982-12-17T00:00:00"
},
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": "Baking"
},
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": "Hiking"
},
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": "Music"
},
{
"memberVariableId": <GUID of member variable>,
"memberId": <GUID of member>,
"memberVariableValue": 55000
}
]
Note: If
memberDataSetType is not specified, a value of
Live is used by default.