get_client_item_prices_m Sample Call and Response
This example shows a client retrieving the pricing for one inventory item in a specific currency, based on the get_client_item_prices_m method defined in plsql_m_r73.yml.
The example looks up the item by its Aria-assigned item number and filters the result to United States dollar pricing. It does not cover a lookup by client-defined SKU, and it does not cover the deprecated filter_client_item_id and return_no_cost_items fields.
Sample call
{
"rest_call": "get_client_item_prices_m",
"output_format": "json",
"client_no": 4009,
"auth_key": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6",
"filter_item_no": 71042,
"filter_currency_cd": "usd"
}
The filter_item_no field and the filter_client_sku field form an alternative-required pair; this example supplies filter_item_no, the Aria-assigned numeric identifier, and omits filter_client_sku. The filter_currency_cd field is optional and, set to usd here, narrows the returned rate schedules to that one currency; omitting it would return pricing for every currency configured for the item. This example omits the filter_client_item_id field and the return_no_cost_items field, both of which carry a deprecate_version and no longer belong in a current integration. The rest_call and output_format fields are added by the REST layer.
Sample response
{
"error_code": 0,
"error_msg": "",
"nso_rate_schedules": [
{
"schedule_no": 55210,
"schedule_name": "Standard USD Rate Schedule",
"currency_cd": "usd",
"is_default": "1",
"tier": [
{
"from": 1,
"to": 1,
"amount": 24.99
}
]
},
{
"schedule_no": 55231,
"schedule_name": "Promotional USD Rate Schedule",
"currency_cd": "usd",
"is_default": "0",
"tier": [
{
"from": 1,
"to": 1,
"amount": 19.99
}
]
}
]
}
An error_code value of zero together with an empty error_msg indicates that Aria found and returned the item's pricing successfully. This example intentionally leaves out the item_rates field entirely; the yml marks item_rates as deprecated as of a prior release, and it also marks the nested schedule field inside item_rates with usage: unused, so neither belongs in a current example. The nso_rate_schedules field is the current rate-schedule structure this method returns, but the yml fragment available for this method does not spell out its nested fields directly; the schedule_no, schedule_name, currency_cd, is_default, and tier field names shown here are carried over from the equivalent, fully documented fields nested elsewhere in this same yml under the deprecated item_rates structure, since they describe the same underlying concept of a rate schedule with tiered pricing. Confirm the exact current field names against the authoritative plsql.yml source before relying on this shape in an integration. The nso_rate_schedules field is an array because an item can have more than one rate schedule in the same currency, such as a standard schedule and a promotional schedule; this example shows two representative entries. The is_default field marks exactly one schedule per currency as the default, shown here as the string value one on the standard schedule and zero on the promotional schedule. This example omits the error_details field.