feat(api): api update (#217)

.stats.yml

@@ -1,2 +1,2 @@
 configured_endpoints: 70
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/conductor%2Fconductor-a0e5d6ca07120cf18c2eb861be2e878ca12055d1fabbe5644538da2aecd113de.yml
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/conductor%2Fconductor-916ce45ffd3c30fced85c7e0831e6c77ca95b645bc99ede03b800c17c7e41a0f.yml

src/conductor/resources/qbd/accounts.py

@@ -414,11 +414,13 @@ def list(
               or multiple using a comma-separated list (e.g., `currencyIds=1,2,3`).
 
           full_names: Filter for specific accounts by their full-name(s), case-insensitive. Like `id`,
-              a `fullName` is a unique identifier for an account, and is formed by by
-              combining the names of its parent objects with its own `name`, separated by
-              colons. For example, if an account is under "Expenses:Utilities" and has the
-              `name` "Electricity", its `fullName` would be "Expenses:Utilities:Electricity".
-              Unlike `name`, `fullName` is guaranteed to be unique across all account objects.
+              `fullName` is a unique identifier for an account, formed by by combining the
+              names of its parent objects with its own `name`, separated by colons. For
+              example, if an account is under "Expenses:Utilities" and has the `name`
+              "Electricity", its `fullName` would be "Expenses:Utilities:Electricity". Unlike
+              `name`, `fullName` is guaranteed to be unique across all account objects. Also,
+              unlike `id`, `fullName` can be arbitrarily changed by the QuickBooks user when
+              modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -886,11 +888,13 @@ async def list(
               or multiple using a comma-separated list (e.g., `currencyIds=1,2,3`).
 
           full_names: Filter for specific accounts by their full-name(s), case-insensitive. Like `id`,
-              a `fullName` is a unique identifier for an account, and is formed by by
-              combining the names of its parent objects with its own `name`, separated by
-              colons. For example, if an account is under "Expenses:Utilities" and has the
-              `name` "Electricity", its `fullName` would be "Expenses:Utilities:Electricity".
-              Unlike `name`, `fullName` is guaranteed to be unique across all account objects.
+              `fullName` is a unique identifier for an account, formed by by combining the
+              names of its parent objects with its own `name`, separated by colons. For
+              example, if an account is under "Expenses:Utilities" and has the `name`
+              "Electricity", its `fullName` would be "Expenses:Utilities:Electricity". Unlike
+              `name`, `fullName` is guaranteed to be unique across all account objects. Also,
+              unlike `id`, `fullName` can be arbitrarily changed by the QuickBooks user when
+              modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.

src/conductor/resources/qbd/classes.py

@@ -250,11 +250,13 @@ def list(
               `"Conductor-End-User-Id: {{END_USER_ID}}"`).
 
           full_names: Filter for specific classes by their full-name(s), case-insensitive. Like `id`,
-              a `fullName` is a unique identifier for a class, and is formed by by combining
-              the names of its parent objects with its own `name`, separated by colons. For
-              example, if a class is under "Department" and has the `name` "Marketing", its
-              `fullName` would be "Department:Marketing". Unlike `name`, `fullName` is
-              guaranteed to be unique across all class objects.
+              `fullName` is a unique identifier for a class, formed by by combining the names
+              of its parent objects with its own `name`, separated by colons. For example, if
+              a class is under "Department" and has the `name` "Marketing", its `fullName`
+              would be "Department:Marketing". Unlike `name`, `fullName` is guaranteed to be
+              unique across all class objects. Also, unlike `id`, `fullName` can be
+              arbitrarily changed by the QuickBooks user when modifying its underlying `name`
+              field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -558,11 +560,13 @@ async def list(
               `"Conductor-End-User-Id: {{END_USER_ID}}"`).
 
           full_names: Filter for specific classes by their full-name(s), case-insensitive. Like `id`,
-              a `fullName` is a unique identifier for a class, and is formed by by combining
-              the names of its parent objects with its own `name`, separated by colons. For
-              example, if a class is under "Department" and has the `name` "Marketing", its
-              `fullName` would be "Department:Marketing". Unlike `name`, `fullName` is
-              guaranteed to be unique across all class objects.
+              `fullName` is a unique identifier for a class, formed by by combining the names
+              of its parent objects with its own `name`, separated by colons. For example, if
+              a class is under "Department" and has the `name` "Marketing", its `fullName`
+              would be "Department:Marketing". Unlike `name`, `fullName` is guaranteed to be
+              unique across all class objects. Also, unlike `id`, `fullName` can be
+              arbitrarily changed by the QuickBooks user when modifying its underlying `name`
+              field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.

src/conductor/resources/qbd/customers.py

@@ -703,12 +703,13 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific customers by their full-name(s), case-insensitive. Like
-              `id`, a `fullName` is a unique identifier for a customer, and is formed by by
-              combining the names of its parent objects with its own `name`, separated by
-              colons. For example, if a customer is under "ABC Corporation" and has the `name`
-              "Website Redesign Project", its `fullName` would be "ABC Corporation:Website
-              Redesign Project". Unlike `name`, `fullName` is guaranteed to be unique across
-              all customer objects.
+              `id`, `fullName` is a unique identifier for a customer, formed by by combining
+              the names of its parent objects with its own `name`, separated by colons. For
+              example, if a customer is under "ABC Corporation" and has the `name` "Website
+              Redesign Project", its `fullName` would be "ABC Corporation:Website Redesign
+              Project". Unlike `name`, `fullName` is guaranteed to be unique across all
+              customer objects. Also, unlike `id`, `fullName` can be arbitrarily changed by
+              the QuickBooks user when modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -1490,12 +1491,13 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific customers by their full-name(s), case-insensitive. Like
-              `id`, a `fullName` is a unique identifier for a customer, and is formed by by
-              combining the names of its parent objects with its own `name`, separated by
-              colons. For example, if a customer is under "ABC Corporation" and has the `name`
-              "Website Redesign Project", its `fullName` would be "ABC Corporation:Website
-              Redesign Project". Unlike `name`, `fullName` is guaranteed to be unique across
-              all customer objects.
+              `id`, `fullName` is a unique identifier for a customer, formed by by combining
+              the names of its parent objects with its own `name`, separated by colons. For
+              example, if a customer is under "ABC Corporation" and has the `name` "Website
+              Redesign Project", its `fullName` would be "ABC Corporation:Website Redesign
+              Project". Unlike `name`, `fullName` is guaranteed to be unique across all
+              customer objects. Also, unlike `id`, `fullName` can be arbitrarily changed by
+              the QuickBooks user when modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.

src/conductor/resources/qbd/date_driven_terms.py

@@ -190,12 +190,13 @@ def list(
               `"Conductor-End-User-Id: {{END_USER_ID}}"`).
 
           full_names: Filter for specific date-driven terms by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for a date-driven term, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if a date-driven term is under "Net 30" and
-              has the `name` "2% 10 Net 30", its `fullName` would be "Net 30:2% 10 Net 30".
-              Unlike `name`, `fullName` is guaranteed to be unique across all date-driven term
-              objects.
+              Like `id`, `fullName` is a unique identifier for a date-driven term, formed by
+              by combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if a date-driven term is under "Net 30" and has the `name`
+              "2% 10 Net 30", its `fullName` would be "Net 30:2% 10 Net 30". Unlike `name`,
+              `fullName` is guaranteed to be unique across all date-driven term objects. Also,
+              unlike `id`, `fullName` can be arbitrarily changed by the QuickBooks user when
+              modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -439,12 +440,13 @@ async def list(
               `"Conductor-End-User-Id: {{END_USER_ID}}"`).
 
           full_names: Filter for specific date-driven terms by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for a date-driven term, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if a date-driven term is under "Net 30" and
-              has the `name` "2% 10 Net 30", its `fullName` would be "Net 30:2% 10 Net 30".
-              Unlike `name`, `fullName` is guaranteed to be unique across all date-driven term
-              objects.
+              Like `id`, `fullName` is a unique identifier for a date-driven term, formed by
+              by combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if a date-driven term is under "Net 30" and has the `name`
+              "2% 10 Net 30", its `fullName` would be "Net 30:2% 10 Net 30". Unlike `name`,
+              `fullName` is guaranteed to be unique across all date-driven term objects. Also,
+              unlike `id`, `fullName` can be arbitrarily changed by the QuickBooks user when
+              modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.

src/conductor/resources/qbd/inventory_items.py

@@ -485,12 +485,13 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific inventory items by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for an inventory item, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if an inventory item is under
-              "Furniture:Kitchen" and has the `name` "Cabinet", its `fullName` would be
-              "Furniture:Kitchen:Cabinet". Unlike `name`, `fullName` is guaranteed to be
-              unique across all inventory item objects.
+              Like `id`, `fullName` is a unique identifier for an inventory item, formed by by
+              combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if an inventory item is under "Furniture:Kitchen" and has
+              the `name` "Cabinet", its `fullName` would be "Furniture:Kitchen:Cabinet".
+              Unlike `name`, `fullName` is guaranteed to be unique across all inventory item
+              objects. Also, unlike `id`, `fullName` can be arbitrarily changed by the
+              QuickBooks user when modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -1043,12 +1044,13 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific inventory items by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for an inventory item, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if an inventory item is under
-              "Furniture:Kitchen" and has the `name` "Cabinet", its `fullName` would be
-              "Furniture:Kitchen:Cabinet". Unlike `name`, `fullName` is guaranteed to be
-              unique across all inventory item objects.
+              Like `id`, `fullName` is a unique identifier for an inventory item, formed by by
+              combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if an inventory item is under "Furniture:Kitchen" and has
+              the `name` "Cabinet", its `fullName` would be "Furniture:Kitchen:Cabinet".
+              Unlike `name`, `fullName` is guaranteed to be unique across all inventory item
+              objects. Also, unlike `id`, `fullName` can be arbitrarily changed by the
+              QuickBooks user when modifying its underlying `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.

src/conductor/resources/qbd/non_inventory_items.py

@@ -366,12 +366,14 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific non-inventory items by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for a non-inventory item, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if a non-inventory item is under "Office
-              Supplies" and has the `name` "Printer Ink Cartridge", its `fullName` would be
-              "Office Supplies:Printer Ink Cartridge". Unlike `name`, `fullName` is guaranteed
-              to be unique across all non-inventory item objects.
+              Like `id`, `fullName` is a unique identifier for a non-inventory item, formed by
+              by combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if a non-inventory item is under "Office Supplies" and has
+              the `name` "Printer Ink Cartridge", its `fullName` would be "Office
+              Supplies:Printer Ink Cartridge". Unlike `name`, `fullName` is guaranteed to be
+              unique across all non-inventory item objects. Also, unlike `id`, `fullName` can
+              be arbitrarily changed by the QuickBooks user when modifying its underlying
+              `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.
@@ -790,12 +792,14 @@ def list(
               previous response. If omitted, the API returns the first page of results.
 
           full_names: Filter for specific non-inventory items by their full-name(s), case-insensitive.
-              Like `id`, a `fullName` is a unique identifier for a non-inventory item, and is
-              formed by by combining the names of its parent objects with its own `name`,
-              separated by colons. For example, if a non-inventory item is under "Office
-              Supplies" and has the `name` "Printer Ink Cartridge", its `fullName` would be
-              "Office Supplies:Printer Ink Cartridge". Unlike `name`, `fullName` is guaranteed
-              to be unique across all non-inventory item objects.
+              Like `id`, `fullName` is a unique identifier for a non-inventory item, formed by
+              by combining the names of its parent objects with its own `name`, separated by
+              colons. For example, if a non-inventory item is under "Office Supplies" and has
+              the `name` "Printer Ink Cartridge", its `fullName` would be "Office
+              Supplies:Printer Ink Cartridge". Unlike `name`, `fullName` is guaranteed to be
+              unique across all non-inventory item objects. Also, unlike `id`, `fullName` can
+              be arbitrarily changed by the QuickBooks user when modifying its underlying
+              `name` field.
 
               NOTE: If you include this parameter, QuickBooks will ignore all other query
               parameters.