Skip to main content
This reference guide covers the technical implementation of pricing models in API calls. For conceptual information and business use cases, see our Pricing Models Guide.

Supported Pricing Model Types

When creating prices via the API, you must specify the type parameter with one of these values: Each pricing type requires its corresponding model parameter to be provided in your API request.

Request Examples

Below are examples of how to structure API requests for various pricing models:
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:

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:
string
required
The unique identifier of the product this price is for. Must be a valid product ID in the format prod_XXXXXXXXXXXXXXXXXXXX.
string
required
The type of pricing model to use. Possible values:
integer
Optional number of trial days before billing begins for this price
object
Optional minimum spending threshold for this price
object
Optional maximum spending threshold for this price
object
Optional discount to apply to this price
string
The fee type classification for this price. Possible values: fixed (flat fee), metered (usage-based). If omitted, defaults to the product's fee type.
string
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.
string
required
The billing interval for this price. Possible values: monthly, quarterly, yearly
string
The billing frequency for this price. Possible values: recurring, one-off. If omitted, defaults to the product's billing frequency.
object
Required when type is unit
object
Required when type is fixed
object
Required when type is tiered
object
Required when type is graduated_tiered
object
Required when type is prepaid_tiered
object
Required when type is prepaid_fixed_tiered
object
Required when type is tiered_percentage
object
Required when type is graduated_percentage
object
Required when type is volume_percentage
boolean
Whether 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.

Using with Subscription Versions

When creating or updating subscription versions, you’ll include pricing model details in your request body. See the Create Subscription Version and Update Subscription Version endpoints for complete examples.