qubesync 0.1.0 → 0.2.0

package/operations/data_ext.d.ts

@@ -0,0 +1,197 @@
+// 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 data ext operations: `qube.dataExt.<action>(connectionId, params, { webhookUrl })`. */
+export declare class DataExt {
+  constructor(client: Client);
+  /**
+   * Create data ext: `POST /connections/{connection_id}/data-exts`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `data_ext_name` (required), `data_ext_value` (required), `list_data_ext_type`, `list_obj_ref`, `other_data_ext_type`, `owner_id` (required), `request_id`, `txn_data_ext_type`, `txn_id`, `txn_line_id`.
+   *
+   * Give exactly one of: (`list_data_ext_type`, `list_obj_ref`), or (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/create-data-ext
+   */
+  create(connectionId: string, params: DataExtCreateParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Delete data ext: `DELETE /connections/{connection_id}/data-exts`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `data_ext_del` (required), `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/delete-data-ext
+   */
+  delete(connectionId: string, params: DataExtDeleteParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Update data ext: `PUT /connections/{connection_id}/data-exts`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `data_ext_name` (required), `data_ext_value` (required), `list_data_ext_type`, `list_obj_ref`, `other_data_ext_type`, `owner_id` (required), `request_id`, `txn_data_ext_type`, `txn_id`, `txn_line_id`.
+   *
+   * Give exactly one of: (`list_data_ext_type`, `list_obj_ref`), or (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/update-data-ext
+   */
+  update(connectionId: string, params: DataExtUpdateParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `data_ext.create`: Create data ext.
+ *
+ * Give exactly one of: (`list_data_ext_type`, `list_obj_ref`), or (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`.
+ */
+export interface DataExtCreateParams {
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * The data in this field. The maximum length of `data_ext_value` will depend on the `data_ext_type` of this data extension. For example, if `data_ext_type` is STR255TYPE, the maximum length of `data_ext_value` is 255 characters. If `data_ext_type` is STR1024TYPE, the maximum size of `data_ext_value` is 1KB.
+   */
+  data_ext_value: string;
+  /**
+   * The type of list object (e.g. Customer) that this data extension is attached to.
+   */
+  list_data_ext_type?: "Account" | "Customer" | "Employee" | "Item" | "OtherName" | "Vendor";
+  /**
+   * Refers to a list object. In a DataExtAdd request, the list object ref must be the same type as the type specified in `list_data_ext_type`. If a `list_obj_ref` aggregate includes both `full_name` and `list_id`, `full_name` will be ignored.
+   */
+  list_obj_ref?: CurrencyRef;
+  /**
+   * Not supported.
+   */
+  other_data_ext_type?: "Company";
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   */
+  owner_id: 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;
+  /**
+   * The type of transaction that the data extension belongs to.
+   */
+  txn_data_ext_type?: "ARRefundCreditCard" | "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;
+  /**
+   * 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;
+}
+
+/**
+ * The params of `data_ext.delete`: Delete data ext.
+ */
+export interface DataExtDeleteParams {
+  /**
+   * DataExt The DataExtAdd request writes data to the specified data extension for the specified object. Before you can use a DataExtAdd message to populate a data-extension field with data, the field must be defined, either through the SDK via a DataExtDefAdd request or via the QuickBooks UI by the interactive user.
+   */
+  data_ext_del: DataExtDel;
+  /**
+   * 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 params of `data_ext.update`: Update data ext.
+ *
+ * Give exactly one of: (`list_data_ext_type`, `list_obj_ref`), or (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`.
+ */
+export interface DataExtUpdateParams {
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * The data in this field. The maximum length of `data_ext_value` will depend on the `data_ext_type` of this data extension. For example, if `data_ext_type` is STR255TYPE, the maximum length of `data_ext_value` is 255 characters. If `data_ext_type` is STR1024TYPE, the maximum size of `data_ext_value` is 1KB.
+   */
+  data_ext_value: string;
+  /**
+   * The type of list object (e.g. Customer) that this data extension is attached to.
+   */
+  list_data_ext_type?: "Account" | "Customer" | "Employee" | "Item" | "OtherName" | "Vendor";
+  /**
+   * Refers to a list object. In a DataExtAdd request, the list object ref must be the same type as the type specified in `list_data_ext_type`. If a `list_obj_ref` aggregate includes both `full_name` and `list_id`, `full_name` will be ignored.
+   */
+  list_obj_ref?: CurrencyRef;
+  /**
+   * Not supported.
+   */
+  other_data_ext_type?: "Company";
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   */
+  owner_id: 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;
+  /**
+   * The type of transaction that the data extension belongs to.
+   */
+  txn_data_ext_type?: "ARRefundCreditCard" | "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;
+  /**
+   * 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;
+}
+
+/**
+ * Give exactly one of: (`list_data_ext_type`, `list_obj_ref`), or (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`.
+ */
+export interface DataExtDel {
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * The type of list object (e.g. Customer) that this data extension is attached to.
+   */
+  list_data_ext_type?: "Account" | "Customer" | "Employee" | "Item" | "OtherName" | "Vendor";
+  /**
+   * Refers to a list object. In a DataExtAdd request, the list object ref must be the same type as the type specified in `list_data_ext_type`. If a `list_obj_ref` aggregate includes both `full_name` and `list_id`, `full_name` will be ignored.
+   */
+  list_obj_ref?: CurrencyRef;
+  /**
+   * Not supported.
+   */
+  other_data_ext_type?: "Company";
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   */
+  owner_id: string;
+  /**
+   * The type of transaction that the data extension belongs to.
+   */
+  txn_data_ext_type?: "ARRefundCreditCard" | "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;
+  /**
+   * 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/data_ext.js

@@ -0,0 +1,50 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks data ext operations. Types: data_ext.d.ts. */
+class DataExt {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Create data ext.
+   * @param {string} connectionId
+   * @param {import("./data_ext").DataExtCreateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/create-data-ext
+   */
+  create(connectionId, params, options) {
+    return this.#client.queue("data_ext.create", connectionId, params, options);
+  }
+
+  /**
+   * Delete data ext.
+   * @param {string} connectionId
+   * @param {import("./data_ext").DataExtDeleteParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/delete-data-ext
+   */
+  delete(connectionId, params, options) {
+    return this.#client.queue("data_ext.delete", connectionId, params, options);
+  }
+
+  /**
+   * Update data ext.
+   * @param {string} connectionId
+   * @param {import("./data_ext").DataExtUpdateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-exts/update-data-ext
+   */
+  update(connectionId, params, options) {
+    return this.#client.queue("data_ext.update", connectionId, params, options);
+  }
+}
+
+module.exports = { DataExt };

package/operations/data_ext_def.d.ts

@@ -0,0 +1,173 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest } from "./types";
+
+/** QuickBooks data ext def operations: `qube.dataExtDef.<action>(connectionId, params, { webhookUrl })`. */
+export declare class DataExtDef {
+  constructor(client: Client);
+  /**
+   * Create data ext def: `POST /connections/{connection_id}/data-ext-defs`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `assign_to_object`, `data_ext_format_string`, `data_ext_list_require`, `data_ext_name` (required), `data_ext_txn_require`, `data_ext_type` (required), `include_ret_element`, `owner_id` (required), `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/create-data-ext-def
+   */
+  create(connectionId: string, params: DataExtDefCreateParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Delete data ext def: `DELETE /connections/{connection_id}/data-ext-defs`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `data_ext_name` (required), `owner_id` (required), `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/delete-data-ext-def
+   */
+  delete(connectionId: string, params: DataExtDefDeleteParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * List data ext defs: `GET /connections/{connection_id}/data-ext-defs`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the query string.
+   *
+   * Fields: `assign_to_object`, `include_ret_element`, `meta_data`, `owner_id`, `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/list-data-ext-defs
+   */
+  query(connectionId: string, params: DataExtDefQueryParams | undefined, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * Update data ext def: `PUT /connections/{connection_id}/data-ext-defs`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `assign_to_object`, `data_ext_format_string`, `data_ext_list_require`, `data_ext_name` (required), `data_ext_new_name`, `data_ext_txn_require`, `include_ret_element`, `owner_id` (required), `remove_from_object`, `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/update-data-ext-def
+   */
+  update(connectionId: string, params: DataExtDefUpdateParams, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `data_ext_def.create`: Create data ext def.
+ */
+export interface DataExtDefCreateParams {
+  assign_to_object?: Array<"ARRefundCreditCard" | "Account" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "Company" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Customer" | "Deposit" | "Employee" | "Estimate" | "InventoryAdjustment" | "Invoice" | "Item" | "ItemReceipt" | "JournalEntry" | "OtherName" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Vendor" | "VendorCredit">;
+  /**
+   * The string format required for the data extension.
+   */
+  data_ext_format_string?: string;
+  /**
+   * If `data_ext_list_require` is true, this data extension field is required to be entered in lists. The default value is false.
+   */
+  data_ext_list_require?: boolean;
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * If `data_ext_txn_require` is true, this data extension field is required to be entered in transaction. The default value is false.
+   */
+  data_ext_txn_require?: boolean;
+  /**
+   * The field’s data type, which corresponds to a qbXML data type. In an IDataExtDefAdd request object, if this is a custom field, `data_ext_type` must be detSTR255TYPE.
+   */
+  data_ext_type: "AMTTYPE" | "DATETIMETYPE" | "INTTYPE" | "PERCENTTYPE" | "PRICETYPE" | "QUANTYPE" | "STR1024TYPE" | "STR255TYPE";
+  include_ret_element?: Array<"AssignToObject" | "DataExtFormatString" | "DataExtID" | "DataExtListRequire" | "DataExtName" | "DataExtTxnRequire" | "DataExtType" | "EditSequence" | "ExternalGUID" | "ListID" | "OwnerID" | "TxnID" | "TxnNumber">;
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   */
+  owner_id: 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;
+}
+
+/**
+ * The params of `data_ext_def.delete`: Delete data ext def.
+ */
+export interface DataExtDefDeleteParams {
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * `owner_id` identifies the extension owner. `owner_id` 0 means a public custom field visible in the QuickBooks UI. A GUID means a private app extension that is not shown in the UI. `owner_id` matching is case-insensitive. To share private extensions across apps, both apps must use the same `owner_id` and `data_ext_name`.
+   */
+  owner_id: 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;
+}
+
+/**
+ * The params of `data_ext_def.query`: List data ext defs.
+ */
+export interface DataExtDefQueryParams {
+  /**
+   * Choose at most one of: `owner_id`, or `assign_to_object`.
+   */
+  assign_to_object?: Array<"ARRefundCreditCard" | "Account" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "Company" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Customer" | "Deposit" | "Employee" | "Estimate" | "InventoryAdjustment" | "Invoice" | "Item" | "ItemReceipt" | "JournalEntry" | "OtherName" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Vendor" | "VendorCredit">;
+  include_ret_element?: Array<"AssignToObject" | "DataExtFormatString" | "DataExtID" | "DataExtListRequire" | "DataExtName" | "DataExtTxnRequire" | "DataExtType" | "OwnerID">;
+  /**
+   * 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";
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   *
+   * Choose at most one of: `owner_id`, or `assign_to_object`.
+   */
+  owner_id?: 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;
+}
+
+/**
+ * The params of `data_ext_def.update`: Update data ext def.
+ */
+export interface DataExtDefUpdateParams {
+  assign_to_object?: Array<"ARRefundCreditCard" | "Account" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "Company" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Customer" | "Deposit" | "Employee" | "Estimate" | "InventoryAdjustment" | "Invoice" | "Item" | "ItemReceipt" | "JournalEntry" | "OtherName" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Vendor" | "VendorCredit">;
+  /**
+   * The string format required for the data extension.
+   */
+  data_ext_format_string?: string;
+  /**
+   * If `data_ext_list_require` is true, this data extension field is required to be entered in lists. The default value is false.
+   */
+  data_ext_list_require?: boolean;
+  /**
+   * The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. Also because `owner_id` and `data_ext_name` together make the data extension unique, and because custom fields all have the same `owner_id` of zero, the `data_ext_name` must be a unique value among existing custom fields.
+   */
+  data_ext_name: string;
+  /**
+   * The new name for this field. Note that in the case of custom fields, `data_ext_new_name` can run into name conflicts, because the name space of custom fields (data extensions with an `owner_id` of 0) is shared by all applications.
+   */
+  data_ext_new_name?: string;
+  /**
+   * If `data_ext_txn_require` is true, this data extension field is required to be entered in transaction. The default value is false.
+   */
+  data_ext_txn_require?: boolean;
+  include_ret_element?: Array<"AssignToObject" | "DataExtFormatString" | "DataExtID" | "DataExtListRequire" | "DataExtName" | "DataExtTxnRequire" | "DataExtType" | "EditSequence" | "ExternalGUID" | "ListID" | "OwnerID" | "TxnID" | "TxnNumber">;
+  /**
+   * `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. Keep private GUIDs confidential unless you intentionally share extensions across apps. If you do share them, both apps must use the same `owner_id` and `data_ext_name`, because that pair uniquely identifies the extension.
+   */
+  owner_id: string;
+  remove_from_object?: Array<"ARRefundCreditCard" | "Account" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "Company" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Customer" | "Deposit" | "Employee" | "Estimate" | "InventoryAdjustment" | "Invoice" | "Item" | "ItemReceipt" | "JournalEntry" | "OtherName" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Vendor" | "VendorCredit">;
+  /**
+   * 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;
+}

package/operations/data_ext_def.js

@@ -0,0 +1,62 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+"use strict";
+
+/** QuickBooks data ext def operations. Types: data_ext_def.d.ts. */
+class DataExtDef {
+  #client;
+
+  /** @param {import("../index").Client} client */
+  constructor(client) {
+    this.#client = client;
+  }
+
+  /**
+   * Create data ext def.
+   * @param {string} connectionId
+   * @param {import("./data_ext_def").DataExtDefCreateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/create-data-ext-def
+   */
+  create(connectionId, params, options) {
+    return this.#client.queue("data_ext_def.create", connectionId, params, options);
+  }
+
+  /**
+   * Delete data ext def.
+   * @param {string} connectionId
+   * @param {import("./data_ext_def").DataExtDefDeleteParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/delete-data-ext-def
+   */
+  delete(connectionId, params, options) {
+    return this.#client.queue("data_ext_def.delete", connectionId, params, options);
+  }
+
+  /**
+   * List data ext defs.
+   * @param {string} connectionId
+   * @param {import("./data_ext_def").DataExtDefQueryParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/list-data-ext-defs
+   */
+  query(connectionId, params, options) {
+    return this.#client.queue("data_ext_def.query", connectionId, params, options);
+  }
+
+  /**
+   * Update data ext def.
+   * @param {string} connectionId
+   * @param {import("./data_ext_def").DataExtDefUpdateParams} params
+   * @param {import("./types").OperationOptions} options
+   * @returns {Promise<import("./types").QueuedRequest>}
+   * @see https://docs.qubesync.com/api-reference/v2/data-ext-defs/update-data-ext-def
+   */
+  update(connectionId, params, options) {
+    return this.#client.queue("data_ext_def.update", connectionId, params, options);
+  }
+}
+
+module.exports = { DataExtDef };

package/operations/date_driven_terms.d.ts

@@ -0,0 +1,141 @@
+// Generated from operations.json by scripts/generate-operations.js: don't edit.
+
+import type { Client } from "../index";
+import type { OperationOptions, QueuedRequest, NameFilter, NameRangeFilter } from "./types";
+
+/** QuickBooks date driven terms operations: `qube.dateDrivenTerms.<action>(connectionId, params, { webhookUrl })`. */
+export declare class DateDrivenTerms {
+  constructor(client: Client);
+  /**
+   * Create date driven terms: `POST /connections/{connection_id}/date-driven-terms`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the JSON body.
+   *
+   * Fields: `day_of_month_due` (required), `discount_day_of_month`, `discount_pct`, `due_next_month_days`, `include_ret_element`, `is_active`, `name` (required), `request_id`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/date-driven-terms/create-date-driven-terms
+   */
+  create(connectionId: string, params: DateDrivenTermsCreateParams, options: OperationOptions): Promise<QueuedRequest>;
+  /**
+   * List date driven terms: `GET /connections/{connection_id}/date-driven-terms`, queued for QuickBooks.
+   *
+   * The answer comes to `webhookUrl` as one webhook.
+   * Params go in the query string.
+   *
+   * Fields: `active_status`, `from_modified_date`, `full_name`, `include_ret_element`, `list_id`, `max_returned`, `meta_data`, `name_filter`, `name_range_filter`, `request_id`, `to_modified_date`.
+   *
+   * Resolves to the queued request.
+   * @see https://docs.qubesync.com/api-reference/v2/date-driven-terms/list-date-driven-terms
+   */
+  query(connectionId: string, params: DateDrivenTermsQueryParams | undefined, options: OperationOptions): Promise<QueuedRequest>;
+}
+
+/**
+ * The params of `date_driven_terms.create`: Create date driven terms.
+ */
+export interface DateDrivenTermsCreateParams {
+  /**
+   * The day of the month when full payment is due with no discount.
+   *
+   * Minimum 1. Maximum 31.
+   */
+  day_of_month_due: number;
+  /**
+   * If the payment is made by this day of the month, then `discount_pct` applies.
+   *
+   * Minimum 1. Maximum 31.
+   */
+  discount_day_of_month?: number;
+  /**
+   * If payment is received by `discount_day_of_month`, then this discount will apply to the payment. `discount_pct` must be between 0 and 100.
+   */
+  discount_pct?: number;
+  /**
+   * Handles cases when an invoice or bill is issued close to its due date. If the invoice or bill is issued within this many days of the due date, payment isn’t due until the following month. For example, with a `day_of_month_due` of 15 and a `due_next_month_days` of 2, an invoice issued on May 13th wouldn’t be due until June 15th.
+   */
+  due_next_month_days?: number;
+  include_ret_element?: Array<"DayOfMonthDue" | "DiscountDayOfMonth" | "DiscountPct" | "DueNextMonthDays" | "EditSequence" | "ExternalGUID" | "IsActive" | "ListID" | "Name" | "OwnerID" | "TimeCreated" | "TimeModified" | "TxnID" | "TxnNumber">;
+  /**
+   * If `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
+   */
+  is_active?: boolean;
+  /**
+   * Name is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope. Hierarchical lists can reuse the same Name in different branches because FullName remains distinct.
+   */
+  name: 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;
+}
+
+/**
+ * The params of `date_driven_terms.query`: List date driven terms.
+ */
+export interface DateDrivenTermsQueryParams {
+  /**
+   * Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is asActiveOnly, which selects only list objects that are active.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   */
+  active_status?: "ActiveOnly" | "All" | "InactiveOnly";
+  /**
+   * Filters results to objects modified on or after this timestamp. QuickBooks Desktop accepts 1970-01-01 through 2038-01-19T03:14:07. If only a date is provided, time defaults to 00:00:00.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   *
+   * Format: date-time.
+   */
+  from_modified_date?: string;
+  /**
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   */
+  full_name?: string[];
+  include_ret_element?: Array<"DayOfMonthDue" | "DiscountDayOfMonth" | "DiscountPct" | "DueNextMonthDays" | "EditSequence" | "IsActive" | "ListID" | "Name" | "TimeCreated" | "TimeModified">;
+  /**
+   * `list_id` and `full_name` both identify a list object. QuickBooks assigns `list_id` when the object is created. `list_id` values are unique within a list type, not globally across all lists. If both `full_name` and `list_id` are supplied in a request, QuickBooks uses `list_id` and ignores `full_name`.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   */
+  list_id?: string[];
+  /**
+   * 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.
+   *
+   * QuickBooks doesn't page this query: at most this many records come back, in one answer, with no sign of whether more matched. Leave it out for every match, in one answer; one over 4 MB as the Web Connector sends it, about 3 MB of qbXML isn't kept (`error_type` `response_too_large`), so narrow a large one with its filters.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). 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 object’s Name.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   */
+  name_filter?: NameFilter;
+  /**
+   * Filters according to the object’s Name.
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   */
+  name_range_filter?: NameRangeFilter;
+  /**
+   * 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;
+  /**
+   * Filters results to objects modified on or before this timestamp. QuickBooks Desktop accepts 1970-01-01 through 2038-01-19T03:14:07. If only a date is provided, time defaults to end-of-day (23:59:59).
+   *
+   * Choose at most one of: `list_id`, or `full_name`, or the set (`active_status`, `from_modified_date`, `max_returned`, `name_filter`, `name_range_filter`, `to_modified_date`). Members of a set combine with each other, not with the other choices.
+   *
+   * Format: date-time.
+   */
+  to_modified_date?: string;
+}