In HubSpot, line items represent individual instances of products on a deal, quote, or other object. The line items endpoints allow you to manage and sync this data.
Scope requirements
In HubSpot, line items are individual instances of products. When a product is attached to a deal or quote, it becomes a line item. You can also create standalone line items that aren’t based on an existing product. The line items endpoints allow you to manage this data and sync it between HubSpot and other systems.Example use case: when creating a set of quotes for sales reps to send to potential buyers, you can use this API to create standalone line items per quote, as well as line items based on existing products.
To create a line item, make a POST request to /crm/objects/2026-03/line_items. In the request body, include the line item’s details, such as name, quantity, and price. You may also want to include additional data in the request body:
To create a line item based on an existing product (created through the products API or in HubSpot), include hs_product_id in the request body.
To include the tax rate for your line item, include its ID as the hs_tax_rate_group_id within the properties field of the request body.
You can also associate the line item with deals, quotes, invoices, payment links, or subscriptions by including an associations array in the request body. For example, the request body below would create a line item named “New standalone line item” that’s associated with a deal (ID: 12345).
Line items belong to one single parent object. If associating objects, line items should be individual to each object. For example, if you’re creating a deal and a quote, you should create one set of line items for the deal, and another set for the quote. This will help streamline CRM data across objects and prevent unexpected data loss when needing to modify line items (e.g., deleting a quote will delete the quote’s line items, and if those line items are associated with a deal, the deal’s line items will also be deleted).
The price specified within the properties field cannot be negative.
Line items support the same tiered pricing model as products. You can create a tiered pricing line item in two ways:
Based on an existing product: include hs_product_id in the request body. The tiered pricing properties are inherited from the product.
Directly on the line item: include hs_pricing_model, hs_tier_ranges, and hs_tier_prices in the properties object of the request body, using the same format as products.
Please note: do not set the price property when using tiered pricing properties on a line item. The line item price will be set based on the tiered pricing properties instead.
To retrieve all tiered pricing properties for a given line item, make a GET request to /crm/objects/2026-03/line_item/{lineItemId}?properties=hs_pricing_model,hs_tier_ranges,hs_tier_pricesThe response will include the tiered pricing properties:
When creating a line item with recurring billing, two properties control billing behavior: recurringbillingfrequency and hs_recurring_billing_period. These properties configure how frequently the customer is charged and for how long (i.e., how many payments).
recurringbillingfrequency: how often the customer is billed. Valid values are weekly, biweekly, monthly, quarterly, per_six_months, annually, per_two_years, per_three_years, per_four_years, and per_five_years.
hs_recurring_billing_period: the total billing duration, in ISO 8601 duration format (PnYnMnD or PnW). Setting this property alongside recurringbillingfrequency limits billing to a fixed number of payments. Omit this property to automatically renew billing until canceled.
The table below shows common combinations and their results. Use PnW (weeks) format with weekly or biweekly frequency, and PnM or PnY (months/years) format with all other frequencies.
recurringbillingfrequency
hs_recurring_billing_period
Result
weekly
P12W
12 weekly payments (12 weeks total)
monthly
P8M
8 monthly payments (8 months total)
quarterly
P1Y
4 quarterly payments (1 year total)
annually
P3Y
3 annual payments (3 years total)
monthly
(not set)
billing renews monthly until canceled
The following example creates a line item with 8 monthly payments. The period P8M represents 8 months, and combined with monthly frequency, results in 8 total payments.
The following example creates an auto-renewing monthly line item with no fixed end. Because hs_recurring_billing_period is omitted, billing continues until the subscription is canceled.
Setting hs_recurring_billing_end_date alone does not create fixed-term billing. Use hs_recurring_billing_period to limit a recurring line item to a specific number of payments.
The hs_recurring_billing_terms property and hs_recurring_billing_number_of_payments are both calculated automatically from the period and frequency. You cannot set them directly.
You can retrieve line items individually or in bulk.
To retrieve a specific line item, make a GET request to /crm/objects/2026-03/line_items/{lineItemId} where lineItemId is the ID of the line item.
To retrieve all line items, make a GET request to /crm/objects/2026-03/line_items.
In the request URL, you can include the following parameters:
Parameter
Description
properties
A comma-separated list of the properties to be returned in the response. If a requested property isn’t defined, it won’t be included in the response. If a requested property is defined but a line item doesn’t have a value, it will be returned as null.
propertiesWithHistory
A comma-separated list of the properties to be returned along with their history of previous values. If a requested property isn’t defined, it won’t be included in the response. If a requested property is defined but a line item doesn’t have a value, it will be returned as null.
To update a line item, make a PATCH request to /crm/objects/2026-03/line_items/{lineItemId}, where lineItemId is the ID of the line item.In the request body, include the property values that you want to update. You cannot update associations through this method. Instead, use the associations API.For example, your request body might look similar to the following:
For a full list of default line item properties, see the Line item object definition. To retrieve all line item properties from your account, including any custom properties, make a GET request to /crm/properties/2026-03/line_items. Learn more about using the properties API.
You can apply a tax rate to individual line items (e.g., a MA Sales tax of 6.25%). Once you configure your tax rate library in your HubSpot account, you can then make a GET request to /tax-rates/v1/tax-rates to fetch all tax rates, or /tax-rates/v1/tax-rates/{taxRateId} to fetch a tax rate by its ID. Your app will need to authorize the tax_rates.read scope to make this request.The resulting response will resemble the following:
Each tax rate object will include the following properties:
Property name
Description
name
The internal descriptor for the tax rate.
percentageRate
The value of the tax rate, expressed as a percentage.
label
The buyer-facing descriptor of the tax rate, shown on the quote, invoice, or other parent objects.
active
A boolean that denotes whether the tax rate can be applied to a new quote or invoice. You might set this to false for a previous year’s tax rate that’s no longer applicable.
id
The ID of the tax rate.
createdAt
An ISO 8601 timestamp denoting when the tax rate was created.
updatedAt
An ISO 8601 timestamp denoting when the tax rate was last updated.
Once you have the ID of the tax rate you want to apply, provide that id for the hs_tax_rate_group_id within the properties field when creating a line item. Learn more about creating line items in the section above.
Last modified on June 29, 2026
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.