Returns new account object, and updated profile.

• Values should be URL encoded.

• “last_name”, “address”, and “account_owner” are required.

  • account_owner value is returned via Authentication.
  • “phone_number” and “email” are required keys, but the values can be empty.
  • Example: last_name=John Doe&address=1 Union St, San Francisco, CA∾count_owner=441&email=☎_number

• Including a valid “lat” and “lng” will create the account using that and skip geocoding the address (although an address is still required).

  • Example: last_name=John Doe&address=1 Union St, San Francisco, CA⪫=43.435175&lng=-83.9912469&email=☎_number

• Include any custom field key/value pairs, using the field mappings from the user profile “datafields” (see "User Profile"). Consider this example of user profile “datafields”:

  {
  "name":"ct",
  "label":"Flag",
  ...
  },
  {
  "name":"ct2",
  "label":"Next Step",
  ...
  },
  {
  "name":"cn3",
  "label":"Sales YTD",
  ...
  },
  …

  • If you want to update the “Next Step” field in your CRM, then you would include the value for custom text field 2 (“name” ct2 in datafields), but the key is “custom_text2”. So our example would be extended like this:

    • last_name=John Doe&address=1 Union St, San Francisco, CA&ct2=the next step&email=☎_number

  • If you have a custom numeric field you want to update, you would just use “custom_numeric3” if “cn3” is the name of the datafield, like this:

    • last_name=John Doe&address=1 Union St, San Francisco, CA&ct2=the next step&cn3=43&email=☎_number

  • Also, names “ct” and “cn” correspond to keys “custom_text” and “custom_numeric” (no number at the end):

    • last_name=John Doe&address=1 Union St, San Francisco, CA&ct2=the next step&cn3=43&ct=somevalue&cn=10&email=☎_number