@stable_sea/sdk 0.2.12 → 0.2.14

package/README.md

@@ -53,10 +53,12 @@ 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.
 
-## Member notifications and support
+## Member administration and personal actions
 
-Use `createStableSeaSessionClient` for personal notifications, preferences and
-business support messages. It uses an existing signed-in business session,
+Use `createStableSeaSessionClient` for onboarding, legal documents, your profile
+and security, team and API-key administration, notifications, preferences and
+business support messages. It uses
+the native sign-in, MFA and business-selection flow,
 not a Live or Test API key. Use `https://api.stablesea.com`; the isolated
 Test-key Sandbox does not serve member sessions.
 
@@ -74,21 +76,75 @@ console.log(feed.data.data);
 ```
 
 Node.js fetch does not retain cookies automatically. Supply your authenticated
-transport; the client does not implement login, refresh or automatic retries.
+transport. Call the typed sign-in and refresh operations explicitly; the client
+does not perform authentication, cookie storage or retries automatically.
 Existing login MFA, business membership, locks and permissions remain in force.
 Member requests do not use the dated financial API contract header.
 
 Member writes use `member.POST`, with each native operation's retry behavior.
-They have no financial `mutation()` helper or idempotency-key replay. After an
+They have no financial `mutation()` helper. Key creation and rotation require
+an `Idempotency-Key`; other operations retain their documented native retry
+behavior. After an
 uncertain message send, match the returned `id` in the thread against the
 `message_id` you sent before resending;
 repeated sends can repeat notifications. Contact submissions must not retry
 automatically. See the [member guide](https://docs.stablesea.com/api/#member-sessions)
 for sign-in, session lifecycle and attachment retrieval, and the
 [member reference](https://docs.stablesea.com/api/member-reference/) for fields.
+
+List members at `GET /identity/members` and manage invitations at
+`/identity/members/invites`. Creation returns invitation details, never the
+redemption token delivered to the invitee. Invitation acceptance uses the
+invitee's email-link token; administrators cannot accept on their behalf.
+Member grants and activation use existing business permissions. Policy settings
+retain their separate launch gate.
+
+Manage Live and Test credentials at `/identity/api_keys`. Use an explicit scope
+list and a unique issuance idempotency key. Test lifecycle operations have no
+extra fresh two-factor prompt; Live operations retain their existing protection.
+Key management requires the same permission as Terminal and never broadens an
+existing credential's scopes implicitly.
+
+Native refresh and extension retain their existing `Success` and `Message`
+response keys. HTTP 200 with `Success: false` is a refusal. Sign-out returns an
+empty HTTP 200 after durable revocation and cookie clearing. Preserve the refresh
+cookie's `/platform_identity_api/auth/token` path; the session countdown is
+advisory, not proof of authentication.
+
 Generated types are exported as `SessionPaths`, `SessionOperations` and
 `SessionComponents`; internal operator and excluded product operations are omitted.
 
+## Business onboarding and documents
+
+Use the member client before issuing an API key. Signup uses the existing
+business-email/OTP flow. After account and authenticator setup, sign in and select
+your business using the same session flow as Terminal.
+
+Read `/onboarding/status` and `/compliance/kyb/fields` to discover the current
+requirements and saved answers. Review registry proposals before confirming
+prefilled answers. Draft writes retain their native revision checks: send the
+field's current `answer_revision` as `expected_answer_revision`, keep the returned
+revision, and reload/review a conflict before another save. Checklist uploads and
+account documents use the existing base64 document operations and limits.
+
+Read pending MSAs at `/compliance/msa/terms`, retrieve each document, and retain
+its version for click-through acceptance. Read agreements before the actual
+authorized signer consents. MSA enrollment
+chooses the existing click-through or embedded-signature workflow. An envelope's
+`executed` status and archived artifacts establish completion; issuing a signing
+URL does not. W-9 signing binds the reviewed prepared-form checksum. Custody
+contract signing requires an explicit `Idempotency-Key`. Provider enrollment,
+business terms, signer authority and compliance review remain enforced; this
+client does not activate a feature or sign as a machine credential. Present the
+[WisdomTree supplemental terms](https://www.wisdomtreeconnect.com/stable-sea-supplemental-terms-of-use)
+before recording the member's explicit consent at `/money/treasury/terms`;
+that route's GET returns acceptance metadata, not the document.
+
+See the [onboarding guide](https://docs.stablesea.com/api/#onboarding) for the
+workflow, field-value encoding and document handling, and the
+[member reference](https://docs.stablesea.com/api/member-reference/) for request
+shapes and native retry rules.
+
 ## Idempotent writes
 
 Create one mutation handle for one logical write. Its `POST` method always sends

package/dist/gen/schema.d.ts

@@ -2284,7 +2284,7 @@ export interface components {
             /** @enum {string} */
             status: "completed" | "pending" | "failed";
             /** @enum {string} */
-            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
+            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "cash_home_transfer" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
             withdrawal?: components["schemas"]["StatementWithdrawal"];
         };
         StatementGeneration: {
@@ -2433,7 +2433,7 @@ export interface components {
              * @description What the movement is. The whole vocabulary a transaction can carry is published; a business only ever sees the members its own activity produces. Pay-ins and payouts are never served on this API.
              * @enum {string}
              */
-            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
+            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "cash_home_transfer" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
         };
         TransactionAssetChange: {
             /** @description The signed net change to the business's settled holdings of this asset, in the asset's own units. Negative amounts decrease holdings; positive amounts increase them. Net of the ledger's fees and taxes, on the same basis /v1/balances reports. For a business with no pay-ins or payouts, summing an asset's amounts across every transaction — not only the completed ones — gives the movement in its settled balance. Pay-ins and payouts are not served on this API but still move /v1/balances, so a business with payments cannot reconcile its balance from transactions alone. */
@@ -2493,7 +2493,7 @@ export interface components {
              * @description What the movement is. The whole vocabulary a transaction can carry is published; a business only ever sees the members its own activity produces. Pay-ins and payouts are never served on this API.
              * @enum {string}
              */
-            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
+            type: "ach_offramp" | "ach_onramp" | "adjustment" | "buy_fund_token" | "buy_fund_token_return" | "buy_fund_token_return_sweep" | "cash_home_transfer" | "deposit_hold" | "deposit_return" | "deposit_reversal" | "fund_cash_subscription" | "fund_dividend_payout" | "fund_distribution_payout" | "fund_gas_tank" | "fund_xlm_reserve" | "gas_tank_refill" | "gas_wallet_funding" | "go_account_conversion" | "go_account_custodial_transfer" | "go_account_external_send" | "held_deposit_release" | "onchain_deposit" | "onchain_withdrawal" | "ramp_fee_refund" | "reclassification" | "sell_fund_token" | "sell_fund_token_return" | "trade_order" | "treasury_booking" | "treasury_wire_credit" | "wire_offramp" | "wire_onramp";
         };
         TransactionFeeReturns: {
             original_transaction_id: string | null;