qubesync 0.1.0 → 0.2.0

package/operations/transfer_inventory.d.ts

@@ -0,0 +1,290 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest, AccountFilter, CurrencyFilter, CurrencyRef, ModifiedDateRangeFilter, RefNumberFilter, RefNumberRangeFilter, TxnDateRangeFilter } from "./types";
+
+/** QuickBooks transfer inventory operations: `qube.transferInventory.<action>(connectionId, params, { webhookUrl })`. */
+export declare class TransferInventory {
+  constructor(client: Client);
+  /**
+   * Create transfer inventory: `POST /connections/{connection_id}/transfer-inventories`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `def_macro`, `external_guid`, `from_inventory_site_ref` (required), `include_ret_element`, `memo`, `ref_number`, `request_id`, `to_inventory_site_ref` (required), `transfer_inventory_line_add`, `txn_date`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/create-transfer-inventory
+   */
+  create(connectionId: string, params: TransferInventoryCreateParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * List transfer inventories: `GET /connections/{connection_id}/transfer-inventories`, queued for QuickBooks.
+   *
+   * QuickBooks answers in pages: each page comes to `webhookUrl` as its own webhook.
+   * Params go in the query string.
+   *
+   * Fields: `account_filter`, `entity_filter`, `include_line_items`, `include_ret_element`, `iterator`, `max_returned`, `meta_data`, `modified_date_range_filter`, `ref_number`, `ref_number_case_sensitive`, `ref_number_filter`, `ref_number_range_filter`, `request_id`, `site_filter`, `txn_date_range_filter`, `txn_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/list-transfer-inventories
+   */
+  query(connectionId: string, params: TransferInventoryQueryParams | undefined, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Update transfer inventory: `PUT /connections/{connection_id}/transfer-inventories`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `edit_sequence` (required), `from_inventory_site_ref`, `include_ret_element`, `memo`, `ref_number`, `request_id`, `to_inventory_site_ref`, `transfer_inventory_line_mod`, `txn_date`, `txn_id` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/update-transfer-inventory
+   */
+  update(connectionId: string, params: TransferInventoryUpdateParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `transfer_inventory.create`: Create transfer inventory.
+ */
+export interface TransferInventoryCreateParams {
+  /**
+   * `def_macro` lets you assign a reusable name to a returned `txn_id` or `txn_line_id` so later requests can reference it with `useMacro`. This feature requires SDK 2.0+.
+   */
+  def_macro?: string;
+  /**
+   * Allows for the attachment of a user defined GUID value.
+   */
+  external_guid?: string;
+  /**
+   * Inventory site that transfer will be taken from.
+   */
+  from_inventory_site_ref: CurrencyRef;
+  include_ret_element?: Array<"EditSequence" | "ExternalGUID" | "FromInventorySiteRef" | "ListID" | "Memo" | "OwnerID" | "RefNumber" | "TimeCreated" | "TimeModified" | "ToInventorySiteRef" | "TransferInventoryLineRet" | "TxnDate" | "TxnID" | "TxnNumber">;
+  /**
+   * Additional information.
+   */
+  memo?: string;
+  /**
+   * `ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique. Some transaction types auto-populate `ref_number` when omitted, based on QuickBooks preferences and numbering state.
+   */
+  ref_number?: string;
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * Inventory site that transfer will be sent to.
+   */
+  to_inventory_site_ref: CurrencyRef;
+  transfer_inventory_line_add?: TransferInventoryLineAdd[];
+  /**
+   * The date of the transaction. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
+   *
+   * Format: date.
+   */
+  txn_date?: string;
+}
+
+/**
+ * The params of `transfer_inventory.query`: List transfer inventories.
+ */
+export interface TransferInventoryQueryParams {
+  /**
+   * Filters according to the account name or `list_id`. If the “Use account numbers” preference is enabled in the QuickBooks company file, you can specify an account number (instead of an account name) for `full_name` and get the account you’re looking for. But if numbers have been used as account names, confusion could arise.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  account_filter?: AccountFilter;
+  /**
+   * An entity refers to a person on the QuickBooks Customer list, Vendor list, Employee list, or Other Names list. You can use an EntityQuery request to get information about all the entities that are set up in the QuickBooks file. In an ARRefundCreditCard query, this must be a customer/customer job.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  entity_filter?: AccountFilter;
+  /**
+   * This filter allows you to omit line items from a query response to get a smaller result. The default value is false, so line items are omitted by default. Set `include_line_items` to true to include line items in the response if you don’t mind getting a larger result.
+   */
+  include_line_items?: boolean;
+  include_ret_element?: Array<"EditSequence" | "ExternalGUID" | "FromInventorySiteRef" | "Memo" | "RefNumber" | "TimeCreated" | "TimeModified" | "ToInventorySiteRef" | "TransferInventoryLineRet" | "TxnDate" | "TxnID" | "TxnNumber">;
+  /**
+   * Page through every match: QuBe Sync asks QuickBooks for each page in turn and sends each to your `webhook_url` as it arrives, all with the same `id`. On by default, with pages of 100 records (25 with `include_line_items`); send `iterator=true` with `max_returned` for another size. Off when you send `iterator=false` (every match in one answer) or `max_returned` alone (at most that many, in one answer). It pages a filtered query only: with `ref_number`, `ref_number_case_sensitive`, `site_filter` or `txn_id` every match comes back in one answer, so leave `iterator` out.
+   */
+  iterator?: boolean;
+  /**
+   * Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `meta_data` query attribute.) If you include a `max_returned` value, it must be at least 1.
+   *
+   * The page size, with `iterator=true`. Sent without `iterator`, or with `iterator=false`, it's a cap instead: at most this many records come back, in one answer, and QuickBooks doesn't say whether more matched.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   *
+   * Minimum 1.
+   */
+  max_returned?: number;
+  /**
+   * Use the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects). Counts are approximate and may vary slightly if records are created or deleted during processing.
+   */
+  meta_data?: "MetaDataAndResponseData" | "MetaDataOnly" | "NoMetaData";
+  /**
+   * Filters according to the dates when transactions were last modified. The `modified_date_range_filter` aggregate isn’t required to contain any elements, but if it is empty, we recommend that you leave it out altogether. Note that the time portion of the `from_modified_date` and `to_modified_date` fields wasn’t supported in qbXML version 1.0 or 1.1.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  modified_date_range_filter?: ModifiedDateRangeFilter;
+  /**
+   * `ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique. Some transaction types auto-populate `ref_number` when omitted, based on QuickBooks preferences and numbering state.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  ref_number?: string[];
+  /**
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  ref_number_case_sensitive?: string[];
+  /**
+   * Filters by `ref_number` range. Numeric-only bounds are compared numerically; otherwise comparison is lexicographic.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  ref_number_filter?: RefNumberFilter;
+  /**
+   * Filters by `ref_number` range. Numeric-only bounds are compared numerically; otherwise comparison is lexicographic.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  ref_number_range_filter?: RefNumberRangeFilter;
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * Allows you to report on Sites.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  site_filter?: CurrencyFilter;
+  /**
+   * Filters according to the original transaction dates.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  txn_date_range_filter?: TxnDateRangeFilter;
+  /**
+   * `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. `txn_id` values are transaction-specific and should not be reused across unrelated transaction types.
+   *
+   * Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`account_filter`, `entity_filter`, `max_returned`, `modified_date_range_filter`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`), or `site_filter`. Members of a set combine with each other, not with the other choices.
+   */
+  txn_id?: string[];
+}
+
+/**
+ * The params of `transfer_inventory.update`: Update transfer inventory.
+ */
+export interface TransferInventoryUpdateParams {
+  /**
+   * `edit_sequence` is a server-generated revision token. It changes each time the object is updated. To modify an existing object, you must send the current `edit_sequence`. If your value is stale, the update is rejected to prevent overwriting newer changes.
+   */
+  edit_sequence: string;
+  /**
+   * Inventory site that transfer will be taken from.
+   */
+  from_inventory_site_ref?: CurrencyRef;
+  include_ret_element?: Array<"EditSequence" | "ExternalGUID" | "FromInventorySiteRef" | "ListID" | "Memo" | "OwnerID" | "RefNumber" | "TimeCreated" | "TimeModified" | "ToInventorySiteRef" | "TransferInventoryLineRet" | "TxnDate" | "TxnID" | "TxnNumber">;
+  /**
+   * Additional information.
+   */
+  memo?: string;
+  /**
+   * `ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique. Some transaction types auto-populate `ref_number` when omitted, based on QuickBooks preferences and numbering state.
+   */
+  ref_number?: string;
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * Inventory site that transfer will be sent to.
+   */
+  to_inventory_site_ref?: CurrencyRef;
+  transfer_inventory_line_mod?: TransferInventoryLineMod[];
+  /**
+   * The date of the transaction. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
+   *
+   * Format: date.
+   */
+  txn_date?: string;
+  /**
+   * `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. `txn_id` values are transaction-specific and should not be reused across unrelated transaction types.
+   */
+  txn_id: string;
+}
+
+export interface TransferInventoryLineAdd {
+  /**
+   * `def_macro` lets you assign a reusable name to a returned `txn_id` or `txn_line_id` so later requests can reference it with `useMacro`. This feature requires SDK 2.0+.
+   */
+  def_macro?: string;
+  /**
+   * Location within the inventory site that transfer will be taken from.
+   */
+  from_inventory_site_location_ref?: CurrencyRef;
+  /**
+   * `item_ref` may accept all item types or a restricted subset, depending on the request. Examples: PurchaseOrder and Bill do not allow discount or sales-tax items; VehicleMileageAdd requires a service or other-charge item; BillingRateAdd requires a service item. If both `full_name` and `list_id` are provided, `full_name` is ignored.
+   */
+  item_ref?: CurrencyRef;
+  /**
+   * The lot number of the asset.
+   *
+   * Choose at most one of: `serial_number`, or `lot_number`.
+   */
+  lot_number?: string;
+  /**
+   * Quantity of items transferred.
+   */
+  quantity_to_transfer?: number;
+  /**
+   * The serial number of the asset.
+   *
+   * Choose at most one of: `serial_number`, or `lot_number`.
+   */
+  serial_number?: string;
+  /**
+   * Location within the inventory site that transfer will be sent to.
+   */
+  to_inventory_site_location_ref?: CurrencyRef;
+}
+
+export interface TransferInventoryLineMod {
+  /**
+   * Location within the inventory site that transfer will be taken from.
+   */
+  from_inventory_site_location_ref?: CurrencyRef;
+  /**
+   * `item_ref` may accept all item types or a restricted subset, depending on the request. Examples: PurchaseOrder and Bill do not allow discount or sales-tax items; VehicleMileageAdd requires a service or other-charge item; BillingRateAdd requires a service item. If both `full_name` and `list_id` are provided, `full_name` is ignored.
+   */
+  item_ref?: CurrencyRef;
+  /**
+   * The lot number of the asset.
+   *
+   * Choose at most one of: `serial_number`, or `lot_number`.
+   */
+  lot_number?: string;
+  /**
+   * Quantity of items transferred.
+   */
+  quantity_to_transfer?: number;
+  /**
+   * The serial number of the asset.
+   *
+   * Choose at most one of: `serial_number`, or `lot_number`.
+   */
+  serial_number?: string;
+  /**
+   * Location within the inventory site that transfer will be sent to.
+   */
+  to_inventory_site_location_ref?: CurrencyRef;
+  /**
+   * Identification number of the transaction line. (`txn_line_id` is supported as of v2.0 of the SDK. With qbXML v1.0 and v1.1, `txn_line_id` is always returned as zero.) If you need to add a new transaction line in a transaction Mod request, you can do so by setting the `txn_line_id` to -1.
+   */
+  txn_line_id: string;
+}

package/operations/transfer_inventory.js

@@ -0,0 +1,50 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks transfer inventory operations. Types: transfer_inventory.d.ts. */
+class TransferInventory {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Create transfer inventory.
+   * @param {string} connectionId
+   * @param {import("./transfer_inventory").TransferInventoryCreateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/create-transfer-inventory
+   */
+  create(connectionId, params, options) {
+    return this.#client.queue("transfer_inventory.create", connectionId, params, options);
+  }
+
+  /**
+   * List transfer inventories (answers in pages, one webhook each).
+   * @param {string} connectionId
+   * @param {import("./transfer_inventory").TransferInventoryQueryParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/list-transfer-inventories
+   */
+  query(connectionId, params, options) {
+    return this.#client.queue("transfer_inventory.query", connectionId, params, options);
+  }
+
+  /**
+   * Update transfer inventory.
+   * @param {string} connectionId
+   * @param {import("./transfer_inventory").TransferInventoryUpdateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/transfer-inventories/update-transfer-inventory
+   */
+  update(connectionId, params, options) {
+    return this.#client.queue("transfer_inventory.update", connectionId, params, options);
+  }
+}
+
+module.exports = { TransferInventory };

package/operations/txn.d.ts

@@ -0,0 +1,39 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest } from "./types";
+
+/** QuickBooks txn operations: `qube.txn.<action>(connectionId, params, { webhookUrl })`. */
+export declare class Txn {
+  constructor(client: Client);
+  /**
+   * Delete txn: `DELETE /connections/{connection_id}/txns`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `request_id`, `txn_del_type` (required), `txn_id` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/txns/delete-txn
+   */
+  delete(connectionId: string, params: TxnDeleteParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `txn.delete`: Delete txn.
+ */
+export interface TxnDeleteParams {
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * The type of transaction to be deleted.
+   */
+  txn_del_type: "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "TimeTracking" | "TransferInventory" | "VehicleMileage" | "VendorCredit";
+  /**
+   * `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. `txn_id` values are transaction-specific and should not be reused across unrelated transaction types.
+   */
+  txn_id: string;
+}

package/operations/txn.js

@@ -0,0 +1,26 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks txn operations. Types: txn.d.ts. */
+class Txn {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Delete txn.
+   * @param {string} connectionId
+   * @param {import("./txn").TxnDeleteParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/txns/delete-txn
+   */
+  delete(connectionId, params, options) {
+    return this.#client.queue("txn.delete", connectionId, params, options);
+  }
+}
+
+module.exports = { Txn };

package/operations/txn_deleted.d.ts

@@ -0,0 +1,44 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest, DeletedDateRangeFilter } from "./types";
+
+/** QuickBooks txn deleted operations: `qube.txnDeleted.<action>(connectionId, params, { webhookUrl })`. */
+export declare class TxnDeleted {
+  constructor(client: Client);
+  /**
+   * List txn deleteds: `GET /connections/{connection_id}/txn-deleteds`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the query string.
+   *
+   * Fields: `deleted_date_range_filter`, `include_ret_element`, `meta_data`, `request_id`, `txn_del_type` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/txn-deleteds/list-txn-deleteds
+   */
+  query(connectionId: string, params: TxnDeletedQueryParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `txn_deleted.query`: List txn deleteds.
+ */
+export interface TxnDeletedQueryParams {
+  /**
+   * Filters according to delete dates (within the last 90 days).
+   */
+  deleted_date_range_filter?: DeletedDateRangeFilter;
+  include_ret_element?: Array<"RefNumber" | "TimeCreated" | "TimeDeleted" | "TxnDelType" | "TxnID">;
+  /**
+   * Use the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects). Counts are approximate and may vary slightly if records are created or deleted during processing.
+   */
+  meta_data?: "MetaDataAndResponseData" | "MetaDataOnly" | "NoMetaData";
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * The type of transaction to be deleted.
+   */
+  txn_del_type: Array<"ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "TimeTracking" | "TransferInventory" | "VehicleMileage" | "VendorCredit">;
+}

package/operations/txn_deleted.js

@@ -0,0 +1,26 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks txn deleted operations. Types: txn_deleted.d.ts. */
+class TxnDeleted {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * List txn deleteds.
+   * @param {string} connectionId
+   * @param {import("./txn_deleted").TxnDeletedQueryParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/txn-deleteds/list-txn-deleteds
+   */
+  query(connectionId, params, options) {
+    return this.#client.queue("txn_deleted.query", connectionId, params, options);
+  }
+}
+
+module.exports = { TxnDeleted };

package/operations/txn_display.d.ts

@@ -0,0 +1,69 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest, CurrencyRef } from "./types";
+
+/** QuickBooks txn display operations: `qube.txnDisplay.<action>(connectionId, params, { webhookUrl })`. */
+export declare class TxnDisplay {
+  constructor(client: Client);
+  /**
+   * Create txn display: `POST /connections/{connection_id}/txn-displays`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `entity_ref`, `request_id`, `txn_display_add_type` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/txn-displays/create-txn-display
+   */
+  create(connectionId: string, params: TxnDisplayCreateParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Update txn display: `PUT /connections/{connection_id}/txn-displays`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `request_id`, `txn_display_mod_type` (required), `txn_id` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/txn-displays/update-txn-display
+   */
+  update(connectionId: string, params: TxnDisplayUpdateParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `txn_display.create`: Create txn display.
+ */
+export interface TxnDisplayCreateParams {
+  /**
+   * A QuickBooks “entity” is a customer, vendor, employee, or person on the QuickBooks “other names” list. Special cases to note: In a BillToPayQuery message, `entity_ref` refers to the vendor name. In JournalCreditLine and JournalDebitLine messages for A/R accounts, `entity_ref` must refer to a customer, or else the transaction won’t be recorded.
+   */
+  entity_ref?: CurrencyRef;
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * Specifies the type of QuickBooks transaction for which to open an edit form in the QuickBooks UI. Notice that some transaction types don’t support the entity reference that “prefills” the form because it would make no sense to do this for certain forms.
+   */
+  txn_display_add_type: "Bill" | "BillPayment" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "VendorCredit";
+}
+
+/**
+ * The params of `txn_display.update`: Update txn display.
+ */
+export interface TxnDisplayUpdateParams {
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * The type of QuickBooks transaction to open for modification in the QuickBooks UI. (`txn_id` specifies the particular transaction.)
+   */
+  txn_display_mod_type: "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "VendorCredit";
+  /**
+   * `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. `txn_id` values are transaction-specific and should not be reused across unrelated transaction types.
+   */
+  txn_id: string;
+}

package/operations/txn_display.js

@@ -0,0 +1,38 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks txn display operations. Types: txn_display.d.ts. */
+class TxnDisplay {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Create txn display.
+   * @param {string} connectionId
+   * @param {import("./txn_display").TxnDisplayCreateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/txn-displays/create-txn-display
+   */
+  create(connectionId, params, options) {
+    return this.#client.queue("txn_display.create", connectionId, params, options);
+  }
+
+  /**
+   * Update txn display.
+   * @param {string} connectionId
+   * @param {import("./txn_display").TxnDisplayUpdateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/txn-displays/update-txn-display
+   */
+  update(connectionId, params, options) {
+    return this.#client.queue("txn_display.update", connectionId, params, options);
+  }
+}
+
+module.exports = { TxnDisplay };

package/operations/txn_void.d.ts

@@ -0,0 +1,39 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest } from "./types";
+
+/** QuickBooks txn void operations: `qube.txnVoid.<action>(connectionId, params, { webhookUrl })`. */
+export declare class TxnVoid {
+  constructor(client: Client);
+  /**
+   * Execute txn void: `POST /connections/{connection_id}/txn-void`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `request_id`, `txn_id` (required), `txn_void_type` (required).
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/txn-void/execute-txn-void
+   */
+  execute(connectionId: string, params: TxnVoidExecuteParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `txn_void.execute`: Execute txn void.
+ */
+export interface TxnVoidExecuteParams {
+  /**
+   * Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
+   */
+  request_id?: string;
+  /**
+   * `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. `txn_id` values are transaction-specific and should not be reused across unrelated transaction types.
+   */
+  txn_id: string;
+  /**
+   * The type of transaction being voided.
+   */
+  txn_void_type: "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "SalesReceipt" | "VendorCredit";
+}

package/operations/txn_void.js

@@ -0,0 +1,26 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks txn void operations. Types: txn_void.d.ts. */
+class TxnVoid {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Execute txn void.
+   * @param {string} connectionId
+   * @param {import("./txn_void").TxnVoidExecuteParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/txn-void/execute-txn-void
+   */
+  execute(connectionId, params, options) {
+    return this.#client.queue("txn_void.execute", connectionId, params, options);
+  }
+}
+
+module.exports = { TxnVoid };