get_auf_status_m Sample Call and Response
This example shows a client checking the upload statistics for a specific client usage file, based on the get_auf_status_m method defined in plsql_m_r73.yml.
The example checks the load status of one named usage file after Aria has finished processing it. It does not cover a request omitting file_name, which the yml marks as optional and which a client might leave out to check the status of the most recently submitted file.
Sample call
{
"rest_call": "get_auf_status_m",
"output_format": "json",
"client_no": 4009,
"auth_key": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6",
"file_name": "usage_20260723_batch01.csv"
}
The file_name field is nullable in the yml and therefore optional, but this example supplies it to target one specific usage file rather than relying on default behavior. The rest_call and output_format fields are added by the REST layer.
Sample response
{
"error_code": 0,
"error_msg": "",
"status_cd": 3,
"load_date_time": "2026-07-23 22:14:07",
"recs_received": 15000,
"recs_loaded": 14988,
"recs_failed": 12
}
An error_code value of zero together with an empty error_msg indicates that Aria found the usage file and returned its load statistics successfully. The status_cd field has no fixed enumeration documented in the yml, so this example uses a plausible client-specific status value of three to represent a completed load; consult your own client configuration for the exact meaning of each status_cd value in your environment. The recs_received, recs_loaded, and recs_failed values together tell a complete story: of the 15000 records received, 14988 loaded successfully and 12 failed. This example omits the nonpublic error_details field.