Account8

AccountPlan6

Aggregation5

Auth1

BalanceChargeSchedule6

Balances8

BalanceTransactionSchedule6

Bill20

BillConfig2

BillGroupingKey5

BillJob5

Charge5

Commitments6

CompoundAggregation5

Contract6

Counter5

CounterAdjustments5

CounterPricing5

CreditReason5

Credits5

Currency5

CustomField2

DataExplorer20

DataExplorerV26

DebitReason5

Debits5

Events4

ExportAdHoc1

ExportDestination6

ExportJob2

ExportSchedule5

External Mapping8

ExternalMappings2

IntegrationConfigs12

IntegrationCredentials5

IntegrationDestinations22

IntegrationRuns7

IntegrationTransformations7

Invitations3

Line Item1

LookupTable5

LookupTableRevision6

LookupTableRevisionData13

Marketplace Integrations1

Measurements6

Meter5

MeterGroup5

Notifications6

OrganizationConfig2

OrgUsers6

PermissionPolicy13

Plan5

PlanGroup5

PlanGroupLink5

PlanTemplate5

Pricing5

Product5

ResourceGroup9

ScheduledEventConfigurations5

ServiceUser6

ServiceUserCredentials6

StatementDefinition5

StatementJob5

Support3

TransactionType5

User1

Pricing

Create Pricing

Changed on Oct 16, 2026

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.

post/organizations/{orgId}/pricings

Request

Base URL
https://api.m3ter.com
Auth
OAuth 2
Authorization codehttps://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize, token URL https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/token
Client credentialsToken URL /oauth/token
TypeScript
https://skmtc.dev/m3ter-com/apis/m3ter-api/docs/organizations/:orgId/pricings/post.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

orgIdstring required

UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.

Request body

aggregationIdstring

UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.

compoundAggregationIdstring

UUID of the Compound Aggregation used to create the Pricing.

type'DEBIT' | 'PRODUCT_CREDIT' | 'GLOBAL_CREDIT'

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.

segmentobject

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 aggregationId parameter 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.

tiersSpanPlanboolean

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.

minimumSpendnumber double

The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.

minimumSpendDescriptionstring

Minimum spend description (displayed on the bill line item).

minimumSpendBillInAdvanceboolean

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.

versioninteger

The 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.

codestring

Unique short code for the Pricing.

planIdstring

UUID of the Plan the Pricing is created for.

planTemplateIdstring

UUID of the Plan Template the Pricing is created for.

cumulativeboolean

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.

startDatestring date-time required

The start date (in ISO-8601 format) for when the Pricing starts to be active for the Plan or the Plan Template.(Required)

endDatestring date-time

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.

descriptionstring

Displayed on Bill line items.

accountingProductIdstring

Optional Product ID this Pricing should be attributed to for accounting purposes

Response

Returns the created Pricing

idstring required

The UUID of the entity.

versioninteger

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.

dtCreatedstring date-time

The DateTime when this item was created (in ISO-8601 format).

dtLastModifiedstring date-time

The DateTime when this item was last modified (in ISO-8601 format).

createdBystring

The ID of the user who created this item.

lastModifiedBystring

The ID of the user who last modified this item.

planIdstring

UUID of the Plan the Pricing is created for.

planTemplateIdstring

UUID of the Plan Template the Pricing was created for.

cumulativeboolean

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.

startDatestring date-time

The start date (in ISO-8601 format) for when the Pricing starts to be active for the Plan of Plan Template.

endDatestring date-time

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.

codestring

Unique short code for the Pricing.

descriptionstring

Displayed on Bill line items.

accountingProductIdstring

aggregationIdstring

UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.

compoundAggregationIdstring

UUID of the Compound Aggregation used to create the Pricing.

type'DEBIT' | 'PRODUCT_CREDIT' | 'GLOBAL_CREDIT'

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.

segmentobject

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.

tiersSpanPlanboolean

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.

minimumSpendnumber double

The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.

minimumSpendDescriptionstring

Minimum spend description (displayed on the bill line item).

minimumSpendBillInAdvanceboolean

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.

aggregationType'SIMPLE' | 'COMPOUND'

segmentStringstring

Changes

Oct 16, 202685c514abc692 Revision changes
- breaking
  the //////// request property type changed from no type to object
- breaking
  the //// request property type changed from no type to object
- breaking
  the //// request property type changed from no type to object
- breaking
  the //// response's property type changed from no type to object for status
- breaking
  the //////// response's property type changed from no type to object for status
- breaking
  the //////////// response's property type changed from no type to object for status
- breaking
  the //////// response's property type changed from no type to object for status
- breaking
  the //// response's property type changed from no type to object for status
- breaking
  the //////// response's property type changed from no type to object for status
- breaking
  the //// response's property type changed from no type to object for status
- breaking
  the response's property type changed from no type to object for status
Aug 1, 20259f9e5f3dbde7 Revision changes
- breaking
  the response property //////// became optional for the status
- breaking
  the response property //// became optional for the status
- breaking
  the response property //////////// became optional for the status
- breaking
  the response property //////// became optional for the status
- breaking
  the response property //////////////// became optional for the status
- breaking
  the response property //////////// became optional for the status
- breaking
  the response property //////////// became optional for the status
- breaking
  the response property //////// became optional for the status

Operation history (3 revisions)

Create Pricing

Request

Path parameters

Request body

Response 200OK

Changes

Response