sync-for-payables: release v10.0.0 (in-house codegen)

sync-for-payables/README.md

@@ -545,14 +545,10 @@ const sdk = new CodatSyncPayables({ debugLogger: console });
 ```
 <!-- End Debugging [debug] -->
 
-<!-- Placeholder for Future Speakeasy SDK Sections -->
-
-
 <!-- Start Codat Support Notes -->
 ## Support
 
 If you encounter any challenges while utilizing our SDKs, please don't hesitate to reach out for assistance. 
 You can raise any issues by contacting your dedicated Codat representative or reaching out to our [support team](mailto:[email protected]).
 We're here to help ensure a smooth experience for you.
 <!-- End Codat Support Notes -->
-### Library generated by [Speakeasy](https://docs.speakeasyapi.dev/docs/using-speakeasy/client-sdks)

sync-for-payables/RELEASES.md

@@ -118,4 +118,21 @@ Based on:
 ### Generated
 - [typescript v9.3.2] sync-for-payables
 ### Releases
-- [NPM v9.3.2] https://www.npmjs.com/package/@codat/sync-for-payables/v/9.3.2 - sync-for-payables
+- [NPM v9.3.2] https://www.npmjs.com/package/@codat/sync-for-payables/v/9.3.2 - sync-for-payables
+
+## 2026-08-25
+### Changes
+Based on:
+- OpenAPI Doc 3.0.0 https://raw.githubusercontent.com/codatio/oas/main/yaml/Codat-Sync-Payables.yaml
+- Codat SDK Codegen
+### Generated
+- [typescript v10.0.0] sync-for-payables
+### Releases
+- [NPM v10.0.0] https://www.npmjs.com/package/@codat/sync-for-payables/v/10.0.0 - sync-for-payables
+
+### Notes
+**Breaking:** only the paths listed in `exports` in `package.json` resolve now. Importing a file by its path inside the package, for example `@codat/sync-for-payables/sdk/models/shared/accountmappingoption.js`, no longer works - import from `@codat/sync-for-payables/sdk/models/shared` or the package root instead.
+
+The zod validation schemas (`*$inboundSchema` / `*$outboundSchema`) are gone and zod is no longer a dependency. Each model now exports `AccountMappingOptionFromJSON`, `AccountMappingOptionToJSON` and `instanceOfAccountMappingOption`.
+
+`SDKError.message` now holds the message on its own. The status code, the content type and the response body are still on the error, as `statusCode`, `contentType` and `body`.

sync-for-payables/USAGE.md

@@ -1,22 +1,28 @@
-<!-- Start SDK Example Usage [usage] -->
-```typescript
-import { CodatSyncPayables } from "@codat/sync-for-payables";
-
-const codatSyncPayables = new CodatSyncPayables({
-  authHeader: "Basic BASE_64_ENCODED(API_KEY)",
-});
-
-async function run() {
-  const result = await codatSyncPayables.companies.list({
-    query: "id=e3334455-1aed-4e71-ab43-6bccf12092ee",
-    orderBy: "-modifiedDate",
-    tags: "region=uk && team=invoice-finance",
-  });
-
-  console.log(result);
-}
-
-run();
-
-```
+<!-- Start SDK Example Usage [usage] -->
+```typescript
+import { CodatSyncPayables } from "@codat/sync-for-payables";
+
+const codatSyncPayables = new CodatSyncPayables({
+  authHeader: "Basic BASE_64_ENCODED(API_KEY)",
+});
+
+async function run() {
+  const result = await codatSyncPayables.bankAccounts.create({
+    companyId: "8a210b68-6988-11ed-a1eb-0242ac120002",
+    connectionId: "2e9d2c44-f675-40ba-8049-353bfcb5e171",
+    bankAccountPrototype: {
+      nominalCode: "22",
+      name: "Plutus - Payables - Bank Account 12",
+      accountType: "Debit",
+      accountNumber: "0120 0440",
+      sortCode: "50-50-50",
+      currency: "GBP",
+    },
+  });
+
+  console.log(result);
+}
+
+run();
+```
 <!-- End SDK Example Usage [usage] -->

sync-for-payables/docs/lib/utils/retryconfig.md

@@ -1,24 +1,24 @@
-# RetryConfig
-
-Allows customizing the default retry configuration. It is only permitted in methods that accept retry policies.
-
-## Fields
-
-| Name                      | Type                                | Description                                                                                | Example     |
-| ------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------ | ----------- |
-| `strategy`                | `"backoff" | "none"`                | The retry strategy to use.                                                                 | `"backoff"` |
-| `backoff`                 | [BackoffStrategy](#backoffstrategy) | When strategy is "backoff", this configurates for the backoff parameters.                  |             |
-| `retryConnectionErrors`   | `*boolean*`                         | When strategy is "backoff", this determines whether or not to retry on connection errors.  | `true`      |
-
-## BackoffStrategy
-
-The backoff strategy allows retrying a request with an exponential backoff between each retry.
-
-### Fields
-
-| Name               | Type         | Description                               | Example  |
-| ------------------ | ------------ | ----------------------------------------- | -------- |
-| `initialInterval`  | `*number*`   | The initial interval in milliseconds.     | `500`    |
-| `maxInterval`      | `*number*`   | The maximum interval in milliseconds.     | `60000`  |
-| `exponent`         | `*number*`   | The exponent to use for the backoff.      | `1.5`    |
+# RetryConfig
+
+Allows customizing the default retry configuration. It is only permitted in methods that accept retry policies.
+
+## Fields
+
+| Name                      | Type                                | Description                                                                                | Example     |
+| ------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------ | ----------- |
+| `strategy`                | `"backoff" | "none"`                | The retry strategy to use.                                                                 | `"backoff"` |
+| `backoff`                 | [BackoffStrategy](#backoffstrategy) | When strategy is "backoff", this configurates for the backoff parameters.                  |             |
+| `retryConnectionErrors`   | `*boolean*`                         | When strategy is "backoff", this determines whether or not to retry on connection errors.  | `true`      |
+
+## BackoffStrategy
+
+The backoff strategy allows retrying a request with an exponential backoff between each retry.
+
+### Fields
+
+| Name               | Type         | Description                               | Example  |
+| ------------------ | ------------ | ----------------------------------------- | -------- |
+| `initialInterval`  | `*number*`   | The initial interval in milliseconds.     | `500`    |
+| `maxInterval`      | `*number*`   | The maximum interval in milliseconds.     | `60000`  |
+| `exponent`         | `*number*`   | The exponent to use for the backoff.      | `1.5`    |
 | `maxElapsedTime`   | `*number*`   | The maximum elapsed time in milliseconds. | `300000` |