Common scenarios: Member Data Use the following use-case scenarios as a guide for creating common API requests. Use an email address to retrieve a member ID The best way to check for the existence of a single member by email address is to use the following request: Request current information about members You can request current information for one or more members at a time by sending the following request. Get an incremental stream of changes to Member Values Monitor any incremental changes to Member Values in your community. POST a Member Variable You can create several Member Variables with different types of properties in a single request. Assign a collection of Member Values Before assigning a collection of Member Values, check to see if a member exists to: Create a member and assign values A member is created when a POST request including memberEmail is sent to /membervalues, as long as that email has never been assigned to a member. Check current Member Values before reassigning Most functionality within the platform relies on the latest Member Values. Since Member Values are a time-series, it is possible to POST the same information for a given member (e.g. City=Vancouver) many times without noticeable functional implications. Doing so will simply record that City=Vancouver was known to be true at these several points in time. Add or remove a Member Variable from the profile Use the profileVariable category to control whether a specific Member Variable will appear in the UI for the purposes of targeting members, exporting data, and reporting.