[sdk-generation-automation]

Changelog

2026-10-28

Added

Expose side on indicative trading rates

Products: Trading

Scope: API + SDKs

• What's new
  Indicative rates and rate offers now include an optional side field indicating whether the price is a buy or a sell.

• Impact
  Customers can tell which direction each returned rate prices; the field is optional, so existing integrations are unaffected.

Affected endpoints:

1. Get rates
2. Get all offers

Add Soroban contract calls on Stellar

Products: Transactions

Scope: API + SDKs

• What's new
  Adds a new transaction operation for invoking Soroban smart contracts on Stellar, where the invocation is submitted as a base64-encoded, unsigned Stellar transaction envelope and the fee asset is XLM or XLM_TEST.

• Impact
  Customers can invoke Stellar Soroban smart contracts through the API; existing transaction operations are unchanged and continue to work.

Affected endpoints:

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

Add Soroban contract calls on Stellar

Products: Off exchanges, Transactions

Scope: API + SDKs

• What's new
  Adds a new transaction operation for invoking Soroban smart contracts on Stellar, where the invocation is submitted as a base64-encoded, unsigned Stellar transaction envelope and the fee asset is XLM or XLM_TEST.

• Impact
  Customers can invoke Stellar Soroban smart contracts through the API; existing transaction operations are unchanged and continue to work.

Affected endpoints:

1. Create a new transaction
2. Estimate transaction fee
3. Add Collateral
4. Remove Collateral
5. Get a specific transaction by external transaction ID
6. Get a specific transaction by Fireblocks transaction ID
7. Get transaction history

Add customer-level address registry default

Products: Compliance

Scope: API + SDKs

• What's new
  Adds endpoints to read, opt in to, and opt out of an organization-wide address registry default that applies to every workspace without its own setting.

• Impact
  Customers can set address registry participation once for the whole organization instead of configuring each workspace, and existing integrations continue to work unchanged.

Affected endpoints:

1. Get your customer's address registry default
2. Opt your customer in to the address registry
3. Opt your customer out of the address registry

Changed

Add BOTH side pricing to trading requests

Products: Trading

Scope: API + SDKs

• What's new
  Trading offer, quote, and rate requests now accept a side value of BOTH to price both directions in a single call, and side is now optional with a default of SELL.

• Impact
  Customers can retrieve buy and sell pricing in one request, and existing integrations keep working because side is only relaxed from required to optional.

Affected endpoints:

1. Get all offers
2. Create a quote
3. Get rates

Fee estimation excludes Soroban calls

Products: Transactions

Scope: API + SDKs

• What's new
  Documents that fee estimation is not available for Stellar Soroban contract call transactions, because the resource fee is determined at transaction creation.

• Impact
  Customers requesting a fee estimate for a Soroban contract call receive an error instead of an estimate; all other operations are unaffected.

Affected endpoints:

1. Estimate transaction fee

Clarify workspace address registry status

Products: Compliance

Scope: API + SDKs

• What's new
  The workspace address registry status is documented as the effective participation value, which follows the organization-wide default when the workspace has made no choice of its own and is opted in when neither is set.

• Impact
  Customers get an accurate view of which workspaces actually participate in the address registry; the response shape is unchanged, so existing integrations keep working.

Affected endpoints:

1. Get address registry status for this workspace
2. Opt this workspace in to the address registry
3. Opt this workspace out of the address registry

Fixed

Fix max spendable amount vault account ID docs

Products: Vaults

Scope: API + SDKs

• What's new
  The documentation for the vault account identifier used when retrieving the maximum spendable amount no longer states that default can be supplied, since only a numeric vault account ID is accepted.

• Impact
  Customers relying on the previous documentation and sending default were receiving an error; the documented behavior now matches the actual API behavior.

Affected endpoints:

1. Get max spendable amount in a transaction

---

[github-actions]

Thank you for raising this! We will review it shortly. (Note that this SDK code is auto generated)