v30.0.0

Changelog

2026-09-08

SDK and CLI updates: TypeScript SDK v30.0.0 • Python SDK v30.0.0 • Java SDK v30.0.0 • CLI v10.0.0

Breaking Change

Add OAuth auth methods and custom fields support

Products: Webhooks V2

Scope: API + SDKs

• What's new
  Adds documentation for merge semantics when updating OAuth credential custom fields, where keys with values are upserted and keys with null are deleted. Adds authMethod field and customJwtClaims, customBodyParams, customHeaders fields to OAuth credential creation requests. Improves description clarity for the delete OAuth credentials response schema. Adds authMethod field and customJwtClaims, customBodyParams, customHeaders update schemas with merge semantics documentation. Adds authMethod as a required response field and read-only arrays for customJwtClaims, customBodyParams, customHeaders showing configured key names without values. Adds schema for custom body parameters on OAuth token requests, supporting string values and write-only storage with read-only name arrays. Adds schema for updating custom body parameters with merge semantics where null deletes a parameter. Adds schema for custom HTTP headers on OAuth token requests, supporting string values with case-insensitive matching and write-only storage. Adds schema for updating custom token request headers with merge semantics where null deletes a header. Adds schema for custom JWT claims used with client_secret_jwt authentication, supporting any JSON type except null with write-only storage. Adds schema for updating custom JWT claims with merge semantics where null deletes a claim.

• Impact
  Customers can use key-by-key merge behavior when updating OAuth credential custom fields.

Affected endpoints:

1. Update OAuth credentials
2. Create OAuth credentials
3. Get all OAuth credentials

Added

Python SDK idle connection timeout support

Products:

Scope: Python-SDK

• What's new
  Connections idle for more than 30 seconds are now reopened instead of reused. the limit is configurable with connection_idle_timeout_sec.

• Impact
  Existing integrations continue to work unchanged.

Affected endpoints:

Add Canton calls and offer response endpoints (beta)

Products: Canton (Beta)

Scope: API + SDKs

• What's new
  Publishes the beta API contract for Canton network calls and offer responses - participant onboarding, end-investor management, allocation operations, and transfer workflows. The endpoints are internal-only in this release and the downstream handlers are not implemented yet.

• Impact
  No customer-facing change yet. The contract is published so SDKs and integrations can be built against it; the routes are gated behind an internal feature flag and unimplemented domains return HTTP 501.

Affected endpoints:

1. Make a Canton call
2. Answer an offer

Add approval requests endpoints (beta)

Products: Approvals (Beta)

Scope: API + SDKs

• What's new
  Adds beta endpoints to list pending approval requests and retrieve individual requests by ID, with support for pagination, quorum status, and cross-user or workspace-wide queries.

• Impact
  Customers can programmatically access and monitor approval requests through the API.

Affected endpoints:

1. List approval requests
2. Get a single approval request

Add webhook OAuth credentials management endpoints

Products: Webhooks V2

Scope: API + SDKs

• What's new
  Adds endpoints to create, list, retrieve, update, and delete reusable OAuth client credential sets that can be shared across multiple webhooks for centralized secret rotation.

• Impact
  Customers can manage OAuth credentials separately from webhooks, enabling easier credential rotation across multiple webhook configurations.

Affected endpoints:

1. Create OAuth credentials
2. Get all OAuth credentials
3. Get OAuth credentials by id
4. Update OAuth credentials
5. Delete OAuth credentials

Add hasNativeAssets field to UTXO outputs

Products: UTXO Management (Beta)

Scope: API + SDKs

• What's new
  Adds an optional boolean field to indicate whether a UTXO carries Cardano native assets (tokens).

• Impact
  Customers can now detect encumbered ADA outputs when managing UTXO-based deposits.

Affected endpoints:

1. Attach or detach labels to/from UTXOs
2. List unspent outputs (UTXOs)

Add completionTime to staking transactions

Products: Staking

Scope: API + SDKs

• What's new
  Adds an optional completionTime field to PositionRelatedTransaction that indicates when Cosmos unbonding is scheduled to end.

• Impact
  Integrators can track when unbonding funds will be released on Cosmos-family chains.

Affected endpoints:

1. List related transactions for a position

Add 5 missing webhook event types to WebhookEvent enum

Products: Webhooks V2

Scope: API + SDKs

• What's new
  Adds 5 new event types to the webhook events enum: transaction.alert.stuck, vault_account.bulk_create_job_started, vault_account.bulk_create_job_ended, vault_account.asset.bulk_add_job_started, and vault_account.asset.bulk_add_job_ended, bringing the enum in sync with deployed webhook-events 1.32.0.

• Impact
  Customers can now subscribe to stuck transaction alerts and bulk vault account/asset job events via the API.

Affected endpoints:

1. Get all notifications by webhook id
2. Create a new webhook
3. Get all webhooks
4. Get notification by id
5. Resend notifications by query
6. Resend failed notifications
7. Get webhook by id
8. Update webhook
9. Delete webhook

Add requestedFeeCurrency to transaction responses

Products: Transactions

Scope: API + SDKs

• What's new
  Adds the requestedFeeCurrency field showing which asset was requested at transaction creation to pay Tempo transaction fees.

• Impact
  Customers can now see which fee-paying asset was originally requested when retrieving transaction details.

Affected endpoints:

1. Get a specific transaction by external transaction ID
2. Get a specific transaction by Fireblocks transaction ID
3. Get transaction history

Changed

Add subProviders field to trading response schemas

Products: Trading (Beta)

Scope: API + SDKs

• What's new
  Introduces response-only schema variants to expose the server-populated subProviders array, which lists the underlying providers a direct-access route is composed of in execution order.

• Impact
  Customers can see which providers are involved in their trading routes without any request-side API changes.

Affected endpoints:

1. Create an order
2. Get orders
3. Get order details
4. Create a quote
5. Get rates
6. Get all offers

Allow null to clear entire custom field maps

Products: Webhooks V2

Scope: API + SDKs

• What's new
  Webhook custom field update schemas now accept null at the field level to clear all entries in a single call, instead of requiring each key to be deleted individually.

• Impact
  Customers can now clear all custom headers, body params, or JWT claims with a single null value instead of listing every key.

Affected endpoints:

1. Update webhook
2. Update OAuth credentials

Add TON/GRAM wallet emptying note to forceSweep field

Products: Off exchanges, Transactions

Scope: API + SDKs

• What's new
  Adds documentation note clarifying that forceSweep combined with treatAsGrossAmount can be used to empty TON/GRAM wallets.

• Impact
  Customers have clearer guidance on how to fully empty TON and GRAM wallets when creating transactions.

Affected endpoints:

1. Create a new transaction
2. Estimate transaction fee
3. Add Collateral
4. Remove Collateral

Add array support for webhook delivery custom headers

Products: Webhooks V2

Scope: API + SDKs

• What's new
  Allows header values to be arrays for sending multiple lines under the same header name, reserves Authorization for OAuth, and clarifies the 10-line limit counts array elements. Updates header value schema to support arrays for merge updates, with clarified delete-via-null semantics and case-insensitive name matching.

• Impact
  Customers can send multi-value headers on webhook notifications using array syntax.

Affected endpoints:

1. Create a new webhook
2. Update webhook

Document FSPM Pro package requirement for findings APIs

Products: Security Posture Management

Scope: API + SDKs

• What's new
  Adds a note clarifying that FSPM security findings endpoints are available only for the FSPM Pro package, not FSPM Basic.

• Impact
  Customers now have clear documentation indicating which FSPM package tier is required to use the security findings endpoints.

Affected endpoints:

1. Get FSPM security findings
2. Get a FSPM security finding by ID
3. Update a FSPM security finding by ID

Update status field example in SecurityFindingDetailed

Products: Security Posture Management

Scope: API + SDKs

• What's new
  Changes the example value for the status field from OPEN to ACCEPTED to better reflect a common workflow state.

• Impact
  SDK documentation examples will show ACCEPTED as the sample status value.

Affected endpoints:

1. Get a FSPM security finding by ID
2. Update a FSPM security finding by ID

Update wallet activation endpoint description

Products: Vaults

Scope: API + SDKs

• What's new
  Removes specific token examples from the wallet activation endpoint description to make it more generic.

• Impact
  No functional changes; documentation now reflects broader applicability of the activation endpoint.

Affected endpoints:

1. Activate a wallet in a vault account

Fixed

Fix empty array examples in FSPM findings API docs

Products: Security Posture Management

Scope: API + SDKs

• What's new
  Replaces empty array examples with realistic sample data showing FSPM security findings with proper structure and values.

• Impact
  API documentation now displays meaningful example data instead of empty arrays.

Affected endpoints:

1. Get FSPM security findings
2. Get a FSPM security finding by ID
3. Update a FSPM security finding by ID