> ## 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. # List all templates > Returns a list of templates. Use the `cursor` parameter to paginate through the results. ## OpenAPI ````yaml GET /quickbooks-desktop/templates openapi: 3.1.0 info: title: Conductor API version: 0.0.1 servers: - url: https://api.conductor.is/v1 security: - BearerAuth: [] paths: /quickbooks-desktop/templates: get: summary: List all templates description: >- Returns a list of templates. Use the `cursor` parameter to paginate through the results. 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 responses: '200': description: Returns a list of templates. headers: Conductor-Request-Id: schema: type: string description: The unique identifier for this API request. example: req_1234567abcdefg required: true content: application/json: schema: type: object properties: objectType: type: string const: list description: The type of object. This value is always `"list"`. example: list url: type: string description: The endpoint URL where this list can be accessed. example: /v1/quickbooks-desktop/templates data: type: array items: $ref: '#/components/schemas/qbd_template' description: The array of templates. nextCursor: type: - string - 'null' description: >- The `nextCursor` is a pagination token returned in the response when you use the `limit` parameter in your request. To retrieve subsequent pages of results, include this token as the value of the `cursor` request parameter in your following API calls. **NOTE**: The `nextCursor` value remains constant throughout the pagination process for a specific list instance; continue to use the same `nextCursor` token in each request to fetch additional pages. example: 12345678-abcd-abcd-example-1234567890ab remainingCount: type: - number - 'null' description: The number of objects remaining to be fetched. example: 10 hasMore: type: boolean description: Indicates whether there are more objects to be fetched. required: - objectType - url - data - nextCursor - remainingCount - hasMore additionalProperties: false 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 templates = await conductor.qbd.templates.list({ conductorEndUserId: 'end_usr_1234567abcdefg', }); console.log(templates.data); - 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 ) templates = conductor.qbd.templates.list( conductor_end_user_id="end_usr_1234567abcdefg", ) print(templates.data) components: schemas: qbd_template: type: object properties: id: type: string description: >- The unique identifier assigned by QuickBooks to this template. This ID is unique across all templates but not across different QuickBooks object types. example: 80000001-1234567890 objectType: type: string const: qbd_template description: The type of object. This value is always `"qbd_template"`. example: qbd_template createdAt: type: string description: >- The date and time when this template 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 template 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 template 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 unique name of this template, unique across all templates. **NOTE**: Templates do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents. example: Professional Invoice isActive: type: boolean description: >- Indicates whether this template is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`. example: true templateType: type: string enum: - bill_payment - build_assembly - credit_memo - estimate - invoice - payment_receipt - purchase_order - sales_order - sales_receipt description: The type of transaction that this template is used for. example: invoice required: - id - objectType - createdAt - updatedAt - revisionNumber - name - isActive - templateType additionalProperties: false title: The Template object x-conductor-object-type: other summary: >- A template is a predefined format for printing certain transactions that a user can define in QuickBooks. The following transaction types support templates: credit memos, estimates, invoices, purchase orders, sales orders, sales receipts, receipt payments, and bill payments. 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).