> ## 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 sales representative > Creates a sales representative that references an existing employee, vendor, or other-name record so it can be assigned on sales forms. ## OpenAPI ````yaml POST /quickbooks-desktop/sales-representatives openapi: 3.1.0 info: title: Conductor API version: 0.0.1 servers: - url: https://api.conductor.is/v1 security: - BearerAuth: [] paths: /quickbooks-desktop/sales-representatives: post: summary: Create a sales representative description: >- Creates a sales representative that references an existing employee, vendor, or other-name record so it can be assigned on sales forms. 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: initial: type: string maxLength: 5 description: |- The initials of this sales representative's name. Maximum length: 5 characters. example: JD isActive: type: boolean description: >- Indicates whether this sales representative is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`. example: true default: true entityId: type: string description: >- The sales representative's corresponding person entity in QuickBooks, stored as either an employee, vendor, or other-name entry. example: 80000001-1234567890 required: - initial - entityId additionalProperties: false responses: '200': description: Returns the newly created sales representative. 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_sales_representative' 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 salesRepresentative = await conductor.qbd.salesRepresentatives.create({ entityId: '80000001-1234567890', initial: 'JD', conductorEndUserId: 'end_usr_1234567abcdefg', }); console.log(salesRepresentative.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 ) sales_representative = conductor.qbd.sales_representatives.create( entity_id="80000001-1234567890", initial="JD", conductor_end_user_id="end_usr_1234567abcdefg", ) print(sales_representative.id) components: schemas: qbd_sales_representative: type: object properties: id: type: string description: >- The unique identifier assigned by QuickBooks to this sales representative. This ID is unique across all sales representatives but not across different QuickBooks object types. example: 80000001-1234567890 objectType: type: string const: qbd_sales_representative description: >- The type of object. This value is always `"qbd_sales_representative"`. example: qbd_sales_representative createdAt: type: string description: >- The date and time when this sales representative 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 sales representative 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 sales representative 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' initial: type: string description: The initials of this sales representative's name. example: JD isActive: type: boolean description: >- Indicates whether this sales representative is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`. example: true entity: type: object 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 sales representative's corresponding person entity in QuickBooks, stored as either an employee, vendor, or other-name entry. example: id: 80000001-1234567890 fullName: John Doe required: - id - objectType - createdAt - updatedAt - revisionNumber - initial - isActive - entity additionalProperties: false title: The Sales Representative object x-conductor-object-type: other summary: >- A sales representative is a person who can be assigned to sales transactions in QuickBooks Desktop. The sales representative corresponds to a separate employee, vendor, or other-name entity in QuickBooks. 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).