get_all_client_receipt_ids_m Sample Call and Response
This example shows a call that retrieves the client receipt identifiers recorded for an entire client over a given date range, based on the plsql_m_r73.yml release definition for get_all_client_receipt_ids_m.
This example includes the two required authentication fields plus the optional date-range filters, and it shows the repeatable receipt array with three representative entries. It does not cover a call made without a date range.
Sample call
{
"rest_call": "get_all_client_receipt_ids_m",
"output_format": "json",
"client_no": 105,
"auth_key": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6",
"start_date_range": "20260101000000",
"end_date_range": "20260630235959"
}
The rest_call and output_format fields are not part of the method’s documented arguments; the REST gateway adds them to every call to identify the method being invoked and to request a JSON response. Unlike get_all_acct_receipt_ids_m, this method does not accept or require an account identifier at all; it returns receipt identifiers entered as input parameters across any API call made under the client, not just calls tied to one account. The optional start_date_range and end_date_range fields each hold a fourteen-character date-time value in yyyymmddhhmmss format, narrowing the results to receipts recorded during the first half of 2026 in this example.
Sample response
{
"error_code": 0,
"error_msg": "OK",
"client_receipt": [
{
"client_receipt_id": "RCPT-2026-0417-001",
"acct_no": 300224981,
"receipt_date": "20260417093012"
},
{
"client_receipt_id": "RCPT-2026-0522-014",
"acct_no": 300230456,
"receipt_date": "20260522141530"
},
{
"client_receipt_id": "BATCH-2026-0601-XYZ",
"receipt_date": "20260601000000"
}
]
}
An error_code of zero with an error_msg of “OK” indicates that Aria returned the client’s receipts successfully. The client_receipt field is an array of receipt records; this example shows three entries to illustrate the repeatable structure, but a client could have many more matching receipts depending on the date range supplied. The first two entries include an acct_no because those receipts were tied to a call scoped to a single account. The third entry omits acct_no entirely, illustrating the method’s own description: when a client receipt does not display an account number, the receipt either did not have an account number in scope, or it was linked to a call that included multiple account IDs. This example leaves out the nonpublic error_details field, which the method returns internally but which does not represent client-facing information.