Supported Pricing Model Types
When creating prices via the API, you must specify thetype parameter with one of these values:
| Type | Description | Model Parameter |
|---|---|---|
unit | Simple per-unit pricing | unitPricingModel |
fixed | Fixed price regardless of usage | fixedPricingModel |
tiered | Pricing tiers based on total usage | tieredPricingModel |
graduated_tiered | Different rates for usage in each tier | graduatedTieredPricingModel |
prepaid_tiered | Pre-purchased units with tier pricing | prepaidTieredPricingModel |
prepaid_fixed_tiered | Pre-purchased fixed package in a tier | prepaidFixedTieredPricingModel |
tiered_percentage | Percentage rates based on tier | tieredPercentagePricingModel |
graduated_percentage | Graduated percentage rates by tier | graduatedPercentagePricingModel |
volume_percentage | Percentage of transaction volume | volumePercentagePricingModel |
Request Examples
Below are examples of how to structure API requests for various pricing models:Request Examples
Request Examples
Unit Pricing Model
Fixed Pricing Model
Tiered Pricing Model
Graduated Tiered Model
Volume Percentage Model
With Discount
With Spending Threshold
Required and Optional Fields
Each pricing model has its own required and optional fields. The table below summarizes the base fields required for all pricing models:| Field | Type | Required | Description |
|---|---|---|---|
productId | string | Yes | The product ID this price applies to |
type | string | Yes | The pricing model type (see table above) |
feeType | string | No | Fee classification: fixed or metered. Defaults to the product’s fee type if omitted |
billingDirection | string | No | When the charge is collected: advance (start of period) or arrears (end of period). Defaults to the product’s payment terms if omitted |
billingInterval | string | Yes | Billing interval: monthly, quarterly, or yearly |
| [Model Parameter] | object | Yes | The specific model parameters (varies by type) |
Common Configuration Options
All pricing models support these additional configuration options:Trial Periods
Spending Thresholds
Discounts
Field Reference
For a complete reference of all available fields for each pricing model type:The unique identifier of the product this price is for. Must be a valid
product ID in the format
prod_XXXXXXXXXXXXXXXXXXXX.The type of pricing model to use. Possible values:
Optional number of trial days before billing begins for this price
Optional minimum spending threshold for this price
Optional maximum spending threshold for this price
Optional discount to apply to this price
The fee type classification for this price. Possible values:
fixed (flat fee), metered (usage-based).
If omitted, defaults to the product's fee type.When the charge is collected relative to the billing period. Possible values:
advance (charged at the start of the billing period),
arrears (charged at the end of the billing period).
This is the price-level equivalent of the product's paymentTerms field.
If omitted, defaults to the product's payment terms.The billing interval for this price. Possible values:
monthly, quarterly, yearlyThe billing frequency for this price. Possible values:
recurring, one-off.
If omitted, defaults to the product's billing frequency.Required when type is
unitRequired when type is
fixedRequired when type is
tieredRequired when type is
graduated_tieredRequired when type is
prepaid_tieredRequired when type is
prepaid_fixed_tieredRequired when type is
tiered_percentageRequired when type is
graduated_percentageRequired when type is
volume_percentageWhether to charge this price on the contract start date for one-off prices. If
false, the price will be charged on the first billing date. Only applicable
for one-off prices in the first subscription version.