get_extended_transaction_info_m Sample Call and Response
This example retrieves the optional transaction qualifiers that were submitted alongside a specific transaction, based on the plsql_m_r73.yml definition file for Aria release 73.
This example includes every required field and shows the transaction's creation details along with a representative set of the qualifiers attached to it, not every qualifier the transaction might carry.
Sample call
{
"rest_call": "get_extended_transaction_info_m",
"output_format": "json",
"client_no": 100234,
"auth_key": "8f3d9c2e1b7a4f6d9e0c1a2b3d4e5f60",
"acct_no": 300118842,
"transaction_id": 9042117
}
The rest_call and output_format fields are envelope fields added by the REST layer; they are not part of the method's own documented arguments. For the account identifier, this example uses acct_no rather than its alternative, client_acct_id. The transaction_id field is required and identifies the transaction whose qualifiers you want to retrieve. The do_logging_ind field is nonpublic and is left out of this example entirely.
Sample response
{
"error_code": 0,
"error_msg": "OK",
"trans_create_user": "csr_agarcia",
"trans_create_date": "2026-06-02 09:14:22",
"extended_transaction_qualifiers": [
{
"qualifier_name": "PromoCode",
"qualifier_value": "SUMMER26"
},
{
"qualifier_name": "SalesRep",
"qualifier_value": "J. Rivera"
}
]
}
An error_code value of 0 and an error_msg value of “OK” indicate the call succeeded. The extended_transaction_qualifiers array would contain one entry for every optional qualifier submitted with the transaction; this example shows two entries, a promotional code and a sales representative name, to illustrate that the qualifier name and value pairs are entirely client-defined. This example leaves out the nonpublic error_details field.