Update Pricing
Update Pricing for the given UUID.
Notes:
- Pricing Plan or Plan Template? Exactly one of
planIdorplanTemplateIdrequest 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
aggregationIdorcompoundAggregationIdrequest 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
typerequest parameter with theDEBIToption, you cannot use negative values forfixedPriceorunitPriceinpricingBandsoroveragePricingBands, and you’ll receive a validation error. If you omit atyperequest parameter aDEBITpricing is created by default and the same constraint on the use of negative values applies.
Authorizations
m3ter supports machine to machine authentication using the clientCredentials OAuth2 flow.
The authorizationCode flow controls access for human users via the m3ter Console application.
Path Parameters
UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
The UUID of the Pricing to update.
Body
The start date (in ISO-8601 format) for when the Pricing starts to be active for the Plan or the Plan Template.(Required)
1The version number of the entity:
- Create entity: Not valid for initial insertion of new entity - do not use for Create. On initial Create, version is set at 1 and listed in the response.
- Update Entity: On Update, version is required and must match the existing version because a check is performed to ensure sequential versioning is preserved. Version is incremented by 1 and listed in the response.
Unique short code for the Pricing.
80^([^[\p{Cntrl}\s]])|([^[\p{Cntrl}\s]][[^[\p{Cntrl}\s]] ]*[^[\p{Cntrl}\s]])$UUID of the Plan the Pricing is created for.
UUID of the Plan Template the Pricing is created for.
Controls whether or not charge rates under a set of pricing bands configured for a Pricing are applied according to each separate band or at the highest band reached.
(Optional). The default value is FALSE.
-
When TRUE, at billing charge rates are applied according to each separate band.
-
When FALSE, at billing charge rates are applied according to highest band reached.
NOTE: Use the cumulative parameter to create the type of Pricing you require. For example, for Tiered Pricing set to TRUE; for Volume Pricing, set to FALSE.
The end date (in ISO-8601 format) for when the Pricing ceases to be active for the Plan or the Plan Template.
(Optional) If not specified, the Pricing remains active indefinitely.
Displayed on Bill line items.
200Optional Product ID this Pricing should be attributed to for accounting purposes
36UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.
36UUID of the Compound Aggregation used to create the Pricing.
36-
DEBIT. Default setting. The amount calculated using the Pricing is added to the bill as a debit.
-
PRODUCT_CREDIT. The amount calculated using the Pricing is added to the bill as a credit (negative amount). To prevent negative billing, the bill will be capped at the total of other line items for the same Product.
-
GLOBAL_CREDIT. The amount calculated using the Pricing is added to the bill as a credit (negative amount). To prevent negative billing, the bill will be capped at the total of other line items for the entire bill, which might include other Products the Account consumes.
IMPORTANT!
- If you use the
typerequest parameter with theDEBIToption, you cannot use negative values forfixedPriceorunitPriceinpricingBandsoroveragePricingBands, and you'll receive a validation error. - If you omit a
typerequest parameter aDEBITpricing is created by default and the same constraint on the use of negative values applies.
DEBIT, PRODUCT_CREDIT, GLOBAL_CREDIT Specifies the segment value which you are defining a Pricing for using this call:
- For each segment value defined on a Segmented Aggregation you must create a separate Pricing and use the appropriate
aggregationIdparameter for the call. - If you specify a segment value that has not been defined for the Aggregation, you'll receive an error.
- If you've defined segment values for the Aggregation using a single wildcard or multiple wildcards, you can create Pricing for these wildcard segment values also.
For more details on creating Pricings for segment values on a Segmented Aggregation using this call, together with some examples, see the Using API Call to Create Segmented Pricings in our User Documentation.
The default value is FALSE.
-
If TRUE, usage accumulates over the entire period the priced Plan is active for the account, and is not reset for pricing band rates at the start of each billing period.
-
If FALSE, usage does not accumulate, and is reset for pricing bands at the start of each billing period.
The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.
x >= 0Minimum spend description (displayed on the bill line item).
200The default value is FALSE.
-
When TRUE, minimum spend is billed at the start of each billing period.
-
When FALSE, minimum spend is billed at the end of each billing period.
(Optional). Overrides the setting at Organization level for minimum spend billing in arrears/in advance.
Specify Prepayment/Balance overage pricing in pricing bands for the case of a Tiered pricing structure. The overage pricing rates will be used to charge for usage if the Account has a Commitment/Prepayment or Balance applied to it and the entire Commitment/Prepayment or Balance amount has been consumed.
Constraints:
- Can only be used for a Tiered pricing structure. If cumulative is FALSE and you defined
overagePricingBands, then you'll receive an error. - If
tiersSpanPlanis set to TRUE for usage accumulates over entire contract period, then cannot be used. - If the Commitment/Prepayement or Balance has an
overageSurchargePercentdefined, then this will override anyoveragePricingBandsyou've defined for the pricing.
Response
Returns the updated Pricing
The UUID of the entity.
The version number:
- Create: On initial Create to insert a new entity, the version is set at 1 in the response.
- Update: On successful Update, the version is incremented by 1 in the response.
The DateTime when this item was created (in ISO-8601 format).
The DateTime when this item was last modified (in ISO-8601 format).
The ID of the user who created this item.
The ID of the user who last modified this item.
UUID of the Plan the Pricing is created for.
UUID of the Plan Template the Pricing was created for.
Controls whether or not charge rates under a set of pricing bands configured for a Pricing are applied according to each separate band or at the highest band reached.
The default value is TRUE.
-
When TRUE, at billing charge rates are applied according to each separate band.
-
When FALSE, at billing charge rates are applied according to highest band reached.
The start date (in ISO-8601 format) for when the Pricing starts to be active for the Plan of Plan Template.
The end date (in ISO-8601 format) for when the Pricing ceases to be active for the Plan or Plan Template.
If not specified, the Pricing remains active indefinitely.
Unique short code for the Pricing.
Displayed on Bill line items.
UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.
UUID of the Compound Aggregation used to create the Pricing.
-
DEBIT. Default setting. The amount calculated using the Pricing is added to the bill as a debit.
-
PRODUCT_CREDIT. The amount calculated using the Pricing is added to the bill as a credit (negative amount). To prevent negative billing, the bill will be capped at the total of other line items for the same Product.
-
GLOBAL_CREDIT. The amount calculated using the Pricing is added to the bill as a credit (negative amount). To prevent negative billing, the bill will be capped at the total of other line items for the entire bill, which might include other Products the Account consumes.
DEBIT, PRODUCT_CREDIT, GLOBAL_CREDIT Name of the segment for which you are defining a Pricing.
For each segment in a segmented aggregation, make a separate call using aggregationId parameter to update a Pricing.
The default value is FALSE.
-
If TRUE, usage accumulates over the entire period the priced Plan is active for the account, and is not reset for pricing band rates at the start of each billing period.
-
If FALSE, usage does not accumulate, and is reset for pricing bands at the start of each billing period.
The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.
Minimum spend description (displayed on the bill line item).
The default value is FALSE.
-
When TRUE, minimum spend is billed at the start of each billing period.
-
When FALSE, minimum spend is billed at the end of each billing period.
(Optional). Overrides the setting at Organization level for minimum spend billing in arrears/in advance.
SIMPLE, COMPOUND The Prepayment/Balance overage pricing in pricing bands for the case of a Tiered pricing structure.