Skip to main content
Aria Knowledge Central

update_contact_m Guide

Updates contact information for Aria accounts or Billing Groups.

API Specification: update_contact_m
Required Fields:
  • <client_no>
  • <auth_key>
  • <acct_no>
  • <contact_ind>

Additional Guidance

Input Fields
Field Name: Notes:
<contact_ind>

When selecting Option 1, the service destination contact is also updated. Also for Option 1, other objects linked to this account contact will also be mapped to the updated contact. For Option 5, other objects linked to this account contact will be retained with the old contact. Specifically, "other objects" above refers to "payment method, billing group statement, and service destination".

Allowable Values
Values Description
1 Account Contact - Other objects linked to this account contact will also be mapped to the updated contact. Here, "other objects" refers specifically to payment method, billing group statement, and service destination.
2 Primary Billing Contact - Primary payment method’s contact of a given billing group.
3 Secondary Billing Contact - Refers to backup payment method’s contact of a given billing group.
4 Statement Contact - Statement contact of a given billing group.
5 Account Contact Only - Other objects linked to this account contact will be retained with the old contact. Here, "other objects" refers specifically to payment method, billing group statement, and service destination.

Error Codes

Error Code/Description Associated Inputs

1001: unexpected error

 

1002: no data found

 

1004: authentication error

<client_no>, <auth_key>

1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)

<acct_no>, <client_acct_id>

1016: invalid input

Additional Comments:  This error can be caused by the wrong type of input; for example, text in a numbers-only field, or specifying a value other than one of the documented allowable values.

<client_no>, <acct_no>, <contact_ind>, <billing_group_no>

1024: invalid date format

Additional Comments: All date inputs must be in yyyy-mm-dd format.

<birthdate>, <application_date>

5017: invalid iso country code

<country_cd>

5018: account in uneditable status

Additional Comments: If the account is in an archived state, edit is not allowed.

 

6021: Invalid state_prov entered

<state_prov>

25020: Illegal characters entered

<auth_key>, <client_billing_group_id>, <first_name>, <middle_initial>, <last_name>, <company_name>, <address1>, <address2>, <address3>, <city>, <locality>, <state_prov>, <country_cd>, <postal_cd>, <phone>, <phone_ext>, <cell_phone>, <work_phone>, <work_phone_ext>, <fax>, <email>, <birthdate>, <client_acct_id>, <application_id>, <application_date>, <alt_caller_id>, <attach_qualifier_option>, <qualifier_name>, <qualifier_value>

26009: Invalid contact Type Indicator

<contact_ind>

26010: Invalid billing group number

<billing_group_no>

26011: Missing billing group identifier

Additional Comments: Billing group is required for contact type 2, 3, and 4.

<billing_group_no>, <client_billing_group_id>
  • Was this article helpful?