Pricings

​

Retrieve Pricing

Function name: m3ter_GetPricing Category: READ HTTP method: GET Destination: m3ter Retrieve the Pricing with the given UUID.

​

Parameters

​

Exits

​

Update Pricing

Function name: m3ter_PutPricing Category: WRITE HTTP method: PUT Destination: m3ter Update Pricing for the given UUID. Notes:

• Pricing Plan or Plan Template? Exactly one of planId or planTemplateId request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
• Using Aggregation or Compound Aggregation for Pricing? Exactly one of aggregationId or compoundAggregationId request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
• Using Negative Values for Pricing? If you use the type request parameter with the DEBIT option, you cannot use negative values for fixedPrice or unitPrice in pricingBands or overagePricingBands, and you’ll receive a validation error. If you omit a type request parameter a DEBIT pricing is created by default and the same constraint on the use of negative values applies.

​

Parameters

​

Exits

​

Delete Pricing

Function name: m3ter_DeletePricing Category: WRITE HTTP method: DELETE Destination: m3ter Delete the Pricing with the given UUID.

​

Parameters

​

Exits

​

List Pricings

Function name: m3ter_ListPricings Category: READ HTTP method: GET (paginated) Destination: m3ter Retrieve a list of Pricings filtered by date/time, Plan ID, PlanTemplate ID, or Pricing ID.

​

Parameters

​

Exits

​

Create Pricing

Function name: m3ter_PostPricing Category: WRITE HTTP method: POST Destination: m3ter Create a new Pricing. Notes:

• Pricing Plan or Plan Template? Exactly one of planId or planTemplateId request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
• Using Aggregation or Compound Aggregation for Pricing? Exactly one of aggregationId or compoundAggregationId request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
• Using Negative Values for Pricing? If you use the type request parameter with the DEBIT option, you cannot use negative values for fixedPrice or unitPrice in pricingBands or overagePricingBands, and you’ll receive a validation error. If you omit a type request parameter a DEBIT pricing is created by default and the same constraint on the use of negative values applies.

​

Parameters

​

Exits