update_acct_status_m Sample Call and Response
This example shows a call that sets the status of a specified account, based on the update_acct_status_m method defined in plsql_m_r73.yml.
The example places an account under a temporary service ban pending a fraud review, effective on a specific date. It does not cover deactivating, archiving, or reactivating an account, nor the billing date reset options this method also supports.
Sample call
{
"rest_call": "update_acct_status_m",
"output_format": "json",
"client_no": 1073,
"auth_key": "b19b2b3a4c5d6e7f8091a2b3c4d5e6f7",
"account_no": 3300521,
"status_cd": 51,
"queue_date": "2026-07-25",
"comments": "Account placed under a temporary service ban pending fraud review."
}
rest_call and output_format are envelope fields added by the REST layer. account_no is one side of an alternative pair with client_acct_id; this example uses the Aria-assigned account number. status_cd uses the enumerated value fifty-one, meaning temporary service ban; other allowable values include zero (deactivated), one (active), thirty-two (registered pending activation), ninety-nine (permanent), and negative ninety-nine (archived). queue_date is one side of an alternative pair with queue_days; this example schedules the change for a specific calendar date rather than a number of days out. Left out of this example: force_bill_date_reset, which when left unset honors the client parameter that controls whether billing dates reset when an account changes from a non-provisionable to a provisionable status; client_receipt_id; and the deprecated alt_do_dunning and status_degrade_date fields, which this example does not use.
Sample response
{
"error_code": 0,
"error_msg": "OK"
}
An error_code of zero together with an error_msg of “OK” indicates that Aria queued the account status change successfully. This method returns no other output fields beyond the error indicators, so there are no arrays or additional sections to illustrate.