As of December 4, 2017, we’ve made changes in the way the value of
price_point_id is handled in API POSTs to record metered component usage or quantity allocations.
Previously, when recording metered component usage or updating quantity allocations, if you supplied a value for the optional
price_point_id, but the price point did not exist, we would accept that value as-is.
Going forward, we will instead return an error message in the API method response.