> ## Documentation Index > Fetch the complete documentation index at: https://docs.conductor.is/llms.txt > Use this file to discover all available pages before exploring further. # Create a service item > Creates a new service item. ## OpenAPI ````yaml POST /quickbooks-desktop/service-items openapi: 3.1.0 info: title: Conductor API version: 0.0.1 servers: - url: https://api.conductor.is/v1 security: - BearerAuth: [] paths: /quickbooks-desktop/service-items: post: summary: Create a service item description: Creates a new service item. parameters: - in: header name: Conductor-End-User-Id description: The ID of the End-User to receive this request. schema: type: string description: The ID of the End-User to receive this request. example: end_usr_1234567abcdefg x-stainless-naming: typescript: method_argument: conductorEndUserId mcp: method_argument: conductorEndUserId required: true requestBody: required: true content: application/json: schema: type: object properties: name: type: string maxLength: 31 description: >- The case-insensitive name of this service item. Not guaranteed to be unique because it does not include the names of its hierarchical parent objects like `fullName` does. For example, two service items could both have the `name` "Web-Design", but they could have unique `fullName` values, such as "Consulting:Web-Design" and "Contracting:Web-Design". Maximum length: 31 characters. example: Web-Design barcode: type: object properties: value: type: string description: The item's barcode value. example: '012345678905' assignEvenIfUsed: type: boolean description: >- Indicates whether to assign the barcode even if it is already used. example: false default: false allowOverride: type: boolean description: Indicates whether to allow the barcode to be overridden. example: false default: false additionalProperties: false description: The service item's barcode. isActive: type: boolean description: >- Indicates whether this service item is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`. example: true default: true classId: type: string description: >- The service item's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. example: 80000001-1234567890 parentId: type: string description: >- The parent service item one level above this one in the hierarchy. For example, if this service item has a `fullName` of "Consulting:Web-Design", its parent has a `fullName` of "Consulting". If this service item is at the top level, this field will be `null`. example: 80000001-1234567890 unitOfMeasureSetId: type: string description: >- The unit-of-measure set associated with this service item, which consists of a base unit and related units. example: 80000001-1234567890 salesTaxCodeId: type: string description: >- The default sales-tax code for this service item, determining whether it is taxable or non-taxable. This can be overridden at the transaction-line level. Default codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales. example: 80000001-1234567890 salesOrPurchaseDetails: type: object properties: description: type: string description: A description of this item. example: Hourly Consulting Service price: type: string description: >- The price at which this item is purchased or sold, represented as a decimal string. example: '19.99' pricePercentage: type: string description: >- The price of this item expressed as a percentage, used instead of `price` when the item's cost is calculated as a percentage of another amount. For example, a service item that costs a percentage of another item's price. example: '10.5' postingAccountId: type: string description: >- The posting account to which transactions involving this item are posted. This could be an income account when selling or an expense account when purchasing. example: 80000001-1234567890 required: - postingAccountId additionalProperties: false description: >- Details for service items that are exclusively sold or exclusively purchased, but not both. This typically applies to non-inventory items (like a purchased office supply that isn't resold) or service items (like consulting services that are sold but not purchased). **IMPORTANT**: You must specify either `salesOrPurchaseDetails` or `salesAndPurchaseDetails` when creating a service item, but never both because an item cannot have both configurations. salesAndPurchaseDetails: type: object properties: salesDescription: type: string description: >- The description of this item that appears on sales forms (e.g., invoices, sales receipts) when sold to customers. example: High-quality steel bolts suitable for construction salesPrice: type: string description: >- The price at which this item is sold to customers, represented as a decimal string. example: '19.99' incomeAccountId: type: string description: >- The income account used to track revenue from sales of this item. example: 80000001-1234567890 purchaseDescription: type: string description: >- The description of this item that appears on purchase forms (e.g., checks, bills, item receipts) when it is ordered or bought from vendors. example: Bulk purchase of steel bolts for inventory purchaseCost: type: string description: >- The cost at which this item is purchased from vendors, represented as a decimal string. example: '15.75' purchaseTaxCodeId: type: string description: >- The tax code applied to purchases of this item. Applicable in regions where purchase taxes are used, such as Canada or the UK. example: 80000001-1234567890 expenseAccountId: type: string description: >- The expense account used to track costs from purchases of this item. example: 80000001-1234567890 preferredVendorId: type: string description: >- The preferred vendor from whom this item is typically purchased. example: 80000001-1234567890 required: - incomeAccountId - expenseAccountId additionalProperties: false description: >- Details for service items that are both purchased and sold, such as reimbursable expenses or inventory items that are bought from vendors and sold to customers. **IMPORTANT**: You must specify either `salesAndPurchaseDetails` or `salesOrPurchaseDetails` when creating a service item, but never both because an item cannot have both configurations. externalId: type: string format: uuid description: >- A globally unique identifier (GUID) you, the developer, can provide for tracking this object in your external system. This field is immutable and can only be set during object creation. **IMPORTANT**: This field must be formatted as a valid GUID; otherwise, QuickBooks will return an error. example: 12345678-abcd-1234-abcd-1234567890ab required: - name additionalProperties: false responses: '200': description: Returns the newly created service item. headers: Conductor-Request-Id: schema: type: string description: The unique identifier for this API request. example: req_1234567abcdefg required: true content: application/json: schema: $ref: '#/components/schemas/qbd_service_item' security: - BearerAuth: [] x-codeSamples: - lang: JavaScript source: |- import Conductor from 'conductor-node'; const conductor = new Conductor({ apiKey: process.env['CONDUCTOR_SECRET_KEY'], // This is the default and can be omitted }); const serviceItem = await conductor.qbd.serviceItems.create({ name: 'Web-Design', conductorEndUserId: 'end_usr_1234567abcdefg', }); console.log(serviceItem.id); - lang: Python source: |- import os from conductor import Conductor conductor = Conductor( api_key=os.environ.get("CONDUCTOR_SECRET_KEY"), # This is the default and can be omitted ) service_item = conductor.qbd.service_items.create( name="Web-Design", conductor_end_user_id="end_usr_1234567abcdefg", ) print(service_item.id) components: schemas: qbd_service_item: type: object properties: id: type: string description: >- The unique identifier assigned by QuickBooks to this service item. This ID is unique across all service items but not across different QuickBooks object types. example: 80000001-1234567890 objectType: type: string const: qbd_service_item description: The type of object. This value is always `"qbd_service_item"`. example: qbd_service_item createdAt: type: string description: >- The date and time when this service item was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user's computer. example: '2025-01-01T12:34:56.000Z' updatedAt: type: string description: >- The date and time when this service item was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user's computer. example: '2025-02-01T12:34:56.000Z' revisionNumber: type: string description: >- The current QuickBooks-assigned revision number of this service item object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you're working with the latest data; otherwise, the update will return an error. example: '1721172183' name: type: string description: >- The case-insensitive name of this service item. Not guaranteed to be unique because it does not include the names of its hierarchical parent objects like `fullName` does. For example, two service items could both have the `name` "Web-Design", but they could have unique `fullName` values, such as "Consulting:Web-Design" and "Contracting:Web-Design". example: Web-Design fullName: type: string description: >- The case-insensitive fully-qualified unique name of this service item, formed by combining the names of its hierarchical parent objects with its own `name`, separated by colons. For example, if a service item is under "Consulting" and has the `name` "Web-Design", its `fullName` would be "Consulting:Web-Design". **NOTE**: Unlike `name`, `fullName` is guaranteed to be unique across all service item objects. However, `fullName` can still be arbitrarily changed by the QuickBooks user when they modify the underlying `name` field. example: Consulting:Web-Design barcode: type: - string - 'null' description: The service item's barcode. example: '012345678905' isActive: type: boolean description: >- Indicates whether this service item is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`. example: true class: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The service item's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. example: id: 80000001-1234567890 fullName: Professional-Services parent: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The parent service item one level above this one in the hierarchy. For example, if this service item has a `fullName` of "Consulting:Web-Design", its parent has a `fullName` of "Consulting". If this service item is at the top level, this field will be `null`. example: id: 80000001-1234567890 fullName: Consulting sublevel: type: number description: >- The depth level of this service item in the hierarchy. A top-level service item has a `sublevel` of 0; each subsequent sublevel increases this number by 1. For example, a service item with a `fullName` of "Consulting:Web-Design" would have a `sublevel` of 1. example: 1 unitOfMeasureSet: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The unit-of-measure set associated with this service item, which consists of a base unit and related units. example: id: 80000001-1234567890 fullName: Weight Units salesTaxCode: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The default sales-tax code for this service item, determining whether it is taxable or non-taxable. This can be overridden at the transaction-line level. Default codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales. example: id: 80000001-1234567890 fullName: Non salesOrPurchaseDetails: oneOf: - $ref: '#/components/schemas/qbd_sales_or_purchase_details' - type: 'null' description: >- Details for service items that are exclusively sold or exclusively purchased, but not both. This typically applies to non-inventory items (like a purchased office supply that isn't resold) or service items (like consulting services that are sold but not purchased). **IMPORTANT**: A service item will have either `salesAndPurchaseDetails` or `salesOrPurchaseDetails`, but never both because an item cannot have both configurations. salesAndPurchaseDetails: oneOf: - $ref: '#/components/schemas/qbd_sales_and_purchase_details' - type: 'null' description: >- Details for service items that are both purchased and sold, such as reimbursable expenses or inventory items that are bought from vendors and sold to customers. **IMPORTANT**: A service item will have either `salesAndPurchaseDetails` or `salesOrPurchaseDetails`, but never both because an item cannot have both configurations. externalId: type: - string - 'null' description: >- A globally unique identifier (GUID) you, the developer, can provide for tracking this object in your external system. This field is immutable and can only be set during object creation. example: 12345678-abcd-1234-abcd-1234567890ab customFields: type: array items: $ref: '#/components/schemas/qbd_custom_field' description: >- The custom fields for the service item object, added as user-defined data extensions, not included in the standard QuickBooks object. required: - id - objectType - createdAt - updatedAt - revisionNumber - name - fullName - barcode - isActive - class - parent - sublevel - unitOfMeasureSet - salesTaxCode - salesOrPurchaseDetails - salesAndPurchaseDetails - externalId - customFields additionalProperties: false title: The Service Item object x-conductor-object-type: item summary: >- A service item represents a billable service offered by or purchased by a business in QuickBooks Desktop. It can track both sales and purchases of services, with customizable pricing, descriptions, and tax settings. Common examples include professional services (consulting, legal advice), labor charges (installation, repairs), recurring services (maintenance contracts), and any non-physical items that generate revenue or expenses. qbd_sales_or_purchase_details: type: object properties: description: type: - string - 'null' description: A description of this item. example: Hourly Consulting Service price: type: - string - 'null' description: >- The price at which this item is purchased or sold, represented as a decimal string. example: '19.99' pricePercentage: type: - string - 'null' description: >- The price of this item expressed as a percentage, used instead of `price` when the item's cost is calculated as a percentage of another amount. For example, a service item that costs a percentage of another item's price. example: '10.5' postingAccount: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The posting account to which transactions involving this item are posted. This could be an income account when selling or an expense account when purchasing. example: id: 80000001-1234567890 fullName: Income:Consulting Services required: - description - price - pricePercentage - postingAccount additionalProperties: false title: The Sales-or-Purchase Details object x-conductor-object-type: nested qbd_sales_and_purchase_details: type: object properties: salesDescription: type: - string - 'null' description: >- The description of this item that appears on sales forms (e.g., invoices, sales receipts) when sold to customers. example: High-quality steel bolts suitable for construction salesPrice: type: - string - 'null' description: >- The price at which this item is sold to customers, represented as a decimal string. example: '19.99' incomeAccount: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: The income account used to track revenue from sales of this item. example: id: 80000001-1234567890 fullName: Income:Product Sales purchaseDescription: type: - string - 'null' description: >- The description of this item that appears on purchase forms (e.g., checks, bills, item receipts) when it is ordered or bought from vendors. example: Bulk purchase of steel bolts for inventory purchaseCost: type: - string - 'null' description: >- The cost at which this item is purchased from vendors, represented as a decimal string. example: '15.75' purchaseTaxCode: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: >- The tax code applied to purchases of this item. Applicable in regions where purchase taxes are used, such as Canada or the UK. example: id: 80000001-1234567890 fullName: GST expenseAccount: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: The expense account used to track costs from purchases of this item. example: id: 80000001-1234567890 fullName: Expenses:Cost of Goods Sold preferredVendor: type: - object - 'null' properties: id: type: - string - 'null' description: >- The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types. example: 80000001-1234567890 fullName: type: - string - 'null' description: >- The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive. example: Parent:Child:Grandchild required: - id - fullName additionalProperties: false description: The preferred vendor from whom this item is typically purchased. example: id: 80000001-1234567890 fullName: Acme Supplies Ltd. required: - salesDescription - salesPrice - incomeAccount - purchaseDescription - purchaseCost - purchaseTaxCode - expenseAccount - preferredVendor additionalProperties: false title: The Sales-and-Purchase Details object x-conductor-object-type: nested qbd_custom_field: type: object properties: ownerId: type: string description: >- The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects. example: '0' name: type: string description: >- The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI. example: Customer Rating type: type: string enum: - amount_type - date_time_type - integer_type - percent_type - price_type - quantity_type - string_1024_type - string_255_type description: The data type of this custom field. example: string_1024_type value: type: string description: >- The value of this custom field. The maximum length depends on the field's data type. example: Premium required: - ownerId - name - type - value additionalProperties: false title: The Custom Field object x-conductor-object-type: nested securitySchemes: BearerAuth: type: http scheme: bearer description: >- Your Conductor secret key using Bearer auth (e.g., `"Authorization: Bearer {{YOUR_SECRET_KEY}}"`). ```` Built with [Mintlify](https://mintlify.com).