@stable_sea/sdk 0.2.40 → 0.2.42

package/README.md

@@ -21,7 +21,7 @@ import { createStableSeaClient } from "@stable_sea/sdk";
 const client = createStableSeaClient({
   apiKey: process.env.STABLE_SEA_API_KEY!,
   baseUrl: process.env.STABLE_SEA_BASE_URL!,
-  version: "2026-10-16",
+  version: "2026-10-26",
 });
 ```
 
@@ -53,9 +53,9 @@ keys and rotations reuse that data.
 WTGXX supports standard and instant settlement. FLTTX supports standard
 settlement; instant orders are refused in both production and sandbox.
 
-Every fund order names the network it settles on, `ethereum` or `stellar`. The
-API never applies a business's default network. A BTC order settles on no network
-and must not name one. The generated `network` type is optional because BTC shares
+Every fund order names the network it settles on, `ethereum`, `stellar` or
+`solana`. The API never applies a business's default network. A BTC order settles
+on no network and must not name one. The generated `network` type is optional because BTC shares
 the request, so the server enforces both rules: a fund order without a network
 fails with `network_required`, and a BTC order with one fails with
 `network_not_applicable`. Sandbox settles on `ethereum`. Instant settlement is
@@ -188,6 +188,12 @@ Test-key Sandbox does not serve member sessions. Test approval review and
 business-rule management use this same business client and session. Your existing
 member permissions apply.
 
+The member client also reads `GET /money/maintenance` using the signed-in
+business session. Its customer response contains `paused`, the custody `revision`
+and optional `updated_ts`, excluding operator reasons or actors. Pause new money
+actions and withhold cached deposit instructions while paused or when this
+authority cannot be read; scope instruction caches by business and revision.
+
 ```ts
 import { createStableSeaSessionClient } from "@stable_sea/sdk";
 
@@ -629,15 +635,32 @@ its first chart refresh. The document's captured financial figures remain readab
   balance, for a business whose WisdomTree Solana switch is on (otherwise
   `FailedPrecondition`); every other fund, and every sell with
   `proceeds_destination: "solana"`, is refused with a 400
-  `invalid_settlement_source`. `/v1` fund orders cannot name Solana yet. A
+  `invalid_settlement_source`. `/v1` fund orders name Solana from the
+  October 26 contract below. A
   fund-trade approval's `fund_route` reports `source: "solana"` and
   `source_network: "solana"` for such a buy.
 
+## October 26 API contract
+
+Update to the latest SDK before placing a fund order on Solana. `POST /v1/orders`
+accepts `network: "solana"` for a fund order, and every order read may return
+`network: "solana"`. A standard WTGXX buy on Solana is funded from the business's
+segregated Solana USDC balance, and a standard WTGXX sell on Solana returns its
+proceeds there, through the same execution path as Terminal. Any other Solana
+order (another fund, or instant settlement), and any Solana order from a business
+outside the WisdomTree Solana program or outside its Solana deposit rollout, ends
+`failed` with `network_not_eligible`. While the platform is still setting up the
+business's Solana wallet, or refilling the SOL it pays network fees with, the order
+stays `pending` and is retried.
+A business that turned Solana off gets `network_not_in_use`. The HTTP request pin
+is `2026-10-26`; the retired `2026-10-16` pin returns
+`400 unsupported_api_version`.
+
 ## October 16 API contract
 
 Update to the latest SDK before placing fund orders. `POST /v1/orders` takes a
 `network` for every fund order and refuses it for BTC, and every order read returns
-`network` (`null` for BTC). The HTTP request pin is `2026-10-16`; the retired
+`network` (`null` for BTC). The HTTP request pin was `2026-10-16`; the retired
 `2026-10-15` pin returns `400 unsupported_api_version`. An order whose network the
 business turned off, or cannot settle on, ends `failed` with `network_not_in_use`
 or `network_not_eligible`.
@@ -649,7 +672,7 @@ with `client.DELETE("/v1/bank_accounts/{id}")`, without a body or idempotency ke
 Read bank and wallet operation `status` instead of `state`. Retrieve issued
 statement content with `GET /v1/statements/{id}`; the `/content` route is retired.
 
-The HTTP request pin is `2026-10-16`. The retired pin returns
+The HTTP request pin is `2026-10-26`. The retired pin returns
 `400 unsupported_api_version`. Existing API keys remain valid; stored key and
 thin-event/webhook versions are preserved.
 
@@ -727,3 +750,40 @@ a queued fee refund is separate from both principal recovery and a settled refun
 The [Sandbox test project](consumer-test/README.md#test-a-withdrawal) includes
 `npm run test:withdrawal` for a saved Test destination. It preserves request keys
 and receipts so an interrupted run can resume without creating a new withdrawal.
+
+## Swap stablecoins
+
+Swaps between USDC and USDT on Ethereum run in your Go Account once Stable Sea
+enables them for your business. Create a key with **Swap stablecoins**
+(`money:swaps_write`) and **Read financial data** (`money:read`). The permission
+appears only while swaps are enabled.
+
+Read `GET /v1/swap_routes` for whether swaps are enabled, each route's limits,
+your swap fee rate and the available balance of each asset. Estimates, quotes and
+swaps are processed in the background: poll each until `status` leaves `pending`.
+
+```ts
+const quoting = client.mutation();
+const { data: quote } = await quoting.POST("/v1/swap_quotes", {
+  body: { route: "ethereum_usdc_usdt", from_asset: "USDC", to_asset: "USDT", amount: "1000" },
+});
+// Retrieve GET /v1/swap_quotes/{id} until status is ready, then review terms.
+const swapping = client.mutation();
+const { data: swap } = await swapping.POST("/v1/swaps", { body: { quote_id: quote!.id } });
+```
+
+`POST /v1/swap_estimates` prices a swap without a binding quote; its `result`
+names the first check a quote would fail in `refusal_reason`. A firm quote lives
+for at most a minute, so submit it promptly; a swap that starts after
+`expires_ts` fails with `quote_expired`. Each quote executes once. A refused
+estimate, quote or swap reports why in `failure_code`.
+
+Follow `GET /v1/swaps/{id}` to `completed` or `failed`. Once booked,
+`transaction_id` names the transaction whose legs carry the amounts actually sent,
+received and charged. After a lost response, resend the same body with the same
+`Idempotency-Key`, or find the swap with `GET /v1/swap_submissions?idempotency_key=…`.
+Never submit the quote again under a new key.
+
+Signed-in members use the member client's `/money/swap_routes`,
+`/money/swap_estimate`, `/money/swap_quotes`, `/money/swaps` and
+`/money/swap_submissions`, with their own buy or sell permission.