update_contact_m Sample Call and Response
This example shows a call that updates contact information for an Aria account, based on the update_contact_m method defined in plsql_m_r73.yml.
The example updates the account-level contact after a customer moved to a new address, changing the name, company name, address, phone number, and email on file. It does not cover updating a billing group’s primary payment method contact, secondary payment method contact, or statement contact, all of which this method also supports through the contact_ind field.
Sample call
{
"rest_call": "update_contact_m",
"output_format": "json",
"client_no": 1073,
"auth_key": "b19b2b3a4c5d6e7f8091a2b3c4d5e6f7",
"acct_no": 3300521,
"contact_ind": 1,
"first_name": "Priya",
"last_name": "Natarajan",
"company_name": "Natarajan Consulting LLC",
"address1": "48 Harborview Lane",
"city": "Portland",
"state_prov": "OR",
"country_cd": "US",
"postal_cd": "97201",
"phone": "5035550148",
"email": "priya.natarajan@example.com"
}
rest_call and output_format are envelope fields added by the REST layer. auth_key is required for this method. acct_no is one side of an alternative pair with client_acct_id; this example uses the Aria-assigned account number. contact_ind uses the enumerated value one, meaning account contact, where other objects linked to the account contact, such as payment methods, billing group statements, and service destinations, are also mapped to the updated contact; other allowable values identify a billing group’s primary payment method contact, secondary payment method contact, statement contact, or an account-contact-only update that does not remap linked objects. Because this example uses contact_ind value one, billing_group_no and client_billing_group_id, which apply only to the billing-group-scoped contact indicator values, are left out. Also left out: middle_initial, address2, address3, locality, phone_ext, cell_phone, work_phone, work_phone_ext, fax, and birthdate.
Sample response
{
"error_code": 0,
"error_msg": "OK",
"contact_no_2": 88123456
}
An error_code of zero together with an error_msg of “OK” indicates that Aria applied the contact update successfully. contact_no_2 is the Aria-assigned unique identifier for the contact affected by this call. The method definition also includes an output field named contact_no that serves the same purpose, but that field is deprecated in favor of contact_no_2 and is left out of this response.