Create a new member with detail

There is no direct members resource that can be called to create a member. Instead, 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.

This will include assignment of a number of other Member Values for System Variables that can subsequently be retrieved.

Typically, at time of creation, you may have other information to provide for the member. By doing so with a new memberEmail, this can all be done together.

Example: POST /membervalues

[
   {
      "memberVariableName": "city",
      "memberEmail": "testuser000001@example.org",
      "memberVariableValue": "New York",
      "effectiveDate": "2016-04-03T00:00:00"
   },
   {
      "memberVariableName": "date of birth",
      "memberEmail": "testuser000001@example.org",
      "memberVariableValue": "1982-03-02T00:00:00",
      "effectiveDate": "2015-08-12T00:00:00"
   },
   {
      "memberVariableName": "areas of interest",
      "memberEmail": "testuser000001@example.org",
      "memberVariableValue": "Reading",
      "effectiveDate": "2015-08-12T00:00:00"
   },
   {
      "memberVariableName": "areas of interest",
      "memberEmail": "testuser000001@example.org",
      "memberVariableValue": "Cycling",
      "effectiveDate": "2015-08-12T00:00:00"
   },
   {
      "memberVariableName": "income",
      "memberEmail": "testuser000001@example.org",
      "memberVariableValue": 50000.25,
      "effectiveDate": "2016-01-19T00:00:00"
   }
]
Tip: You can specify the header X-WebApi-Return-Resource=true which will cause the full Member Values to be returned in the response body. Use this header to extract information such as the memberId for the newly created member.
Note: Including effectiveDate is optional but recommended if you know when this information was valid. If you omit effectiveDate, the current time will be used.