Skip to main content

Query Processed Usage


Query Processed Usage

Use case

You can query the Processed Usage object synchronously through SOAP API to retrieve billed usage records. If the following Billing Rule is used, “Round and determine a price for usage records individually when rating usage charges?”, these records will carry the price per usage record that was determined during billing.

Available fields

The following fields on the Processed Usage object can be accessed from the SOAP API query. Note that WSDL Version 114 or higher is required when making the query call.

  • AccountId
  • BillingPeriodStartDate
  • BillingPeriodEndDate
  • CreatedById
  • CreatedDate
  • InvoiceItemId
  • Quantity
  • RatingAmount
  • SubscriptionId
  • RatePlanChargeId
  • UpdatedById
  • UpdatedDate
  • UsageID

You can use all of these fields to specify conditions when fetching data. However, the Quantity and RatingAmount fields only have value when the Round and determine a price for usage records individually when rating usage charges? billing rule is set to Yes.


The following is an example of the request body and the response body when querying the Processed Usage object against a specific account.


     <api:queryString>select AccountId, BillingPeriodStartDate, BillingPeriodEndDate, CreatedById, CreatedDate, InvoiceItemId, Quantity, RatingAmount, SubscriptionId, RatePlanChargeId, UpdatedById, UpdatedDate, UsageID from ProcessedUsage where AccountId = '402880e77d2e215d017d2e8bfffd0012'and InvoiceItemId = '402880e77d2e215d017d2ec97b1b00cb'</api:queryString>


    <ns1:queryResponse xmlns:ns1="">
    <ns1:queryLocator xmlns:xsi="" xsi:nil="1" />
    <ns1:records xmlns:ns2="" xmlns:xsi="" xsi:type="ns2:ProcessedUsage">