Prospect Update Response in the JSON Format
The following code snippet illustrates how the attribute/value pairs should be structured while receiving the prospect update response in the JSON format:
{
"C1-ADDPROSPERSON"
{
"prospectPersonId" :""
"actionFlag" :"",
"prospectPersonName" :"",
"division" :"",
"customerSegment" :"",
"customerTier" :"",
"accessGroup" :"",
"emailAddress" :"",
"status" :"",
"birthDate" :"",
"address1" :"",
"address2" :"",
"address3" :"",
"address4" :"",
"city" :"",
"state" :"",
"country" :"",
"postal" :"",
"prosPerIdentifierList"
{
"personIdNumber" :"",
"persIsPrimaryId" :"",
"idType" :"",
}
"prosChildRelationList"
{
"childPersonId" :"",
"personRelationshipType" :"",
"childPerType" :"",
"division" :"",
"childPersonIdType" :"",
"childPersonIdNumber" :"",
"endDate" :"",
"startDate" :"",
}
"prosParentPerRelationList"
{
"parentPersonId" :"",
"personRelationshipType" :"",
"parentPerType" :"",
"division" :"",
"parentPersonIdType" :"",
"parentPersonIdNumber" :"",
"endDate" :"",
"startDate" :"",
}
"prosAccountList"
{
"personId" :"",
"prospectAccountId" :"",
"customerClass" :"",
"accountDivision" :"",
"status" :"",
"setUpDate" :"",
"currency" :"",
"billCycle" :"",
"accountAccessGroup" :"",
"prosAcctCharacteristicList"
{
"characteristicValue" :"",
"effectiveDate" :"",
"characteristicType" :"",
}
"prosAcctIdentifierList"
{
"accountIdentifierType" :"",
"isPrimaryId" :"",
"accountNumber" :"",
}
}
"prosPerCharactersticList"
{
"personcharacteristicValue" :"",
"personEffectiveDate" :"",
"personCharType" :"",
}
}
}Related Topics
| For more information on... | See... |
|---|---|
| Prospect update request and response attribute/value pairs in the JSON format | Prospect Update Request and Response - Attribute/Value Pairs in the JSON Format |
| Sample prospect update request and response in the JSON format | Sample Prospect Update Request and Response in the JSON Format |