Generated SDK #2809037023 (major)

[sdk-generation-automation]

Changelog

2026-09-01

Breaking Change

Fix validBefore/validAfter semantics in TRLink policy rules

Products: Transactions

Scope: API + SDKs

• What's new
  Corrects the documentation for validBefore and validAfter fields to accurately describe their behavior as relative durations (seconds since wait/screening step started) rather than absolute Unix timestamps.

• Impact
  Customers should update their implementations to use relative durations in seconds instead of Unix timestamps for these fields.

Affected endpoints:

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

Fix validBefore/validAfter semantics in TRLink policy rules

Products: TRLink

Scope: API + SDKs

• What's new
  Corrects the documentation for validBefore and validAfter fields to accurately describe their behavior as relative durations (seconds since wait/screening step started) rather than absolute Unix timestamps.

• Impact
  Customers should update their implementations to use relative durations in seconds instead of Unix timestamps for these fields.

Affected endpoints:

1. Get TRLink policy

Fix validBefore/validAfter semantics in TRLink policy rules

Products: Compliance

Scope: API + SDKs

• What's new
  Corrects the documentation for validBefore and validAfter fields to accurately describe their behavior as relative durations (seconds since wait/screening step started) rather than absolute Unix timestamps.

• Impact
  Customers should update their implementations to use relative durations in seconds instead of Unix timestamps for these fields.

Affected endpoints:

1. Provides all the compliance details for the given screened transaction.

Remove type field from security finding responses

Products: Security Posture Management

Scope: API + SDKs

• What's new
  Removes the type field from security finding schemas and updates example data to reflect a different finding scenario.

• Impact
  Clients should no longer expect the type field in security finding responses and must update any code that depends on this field.

Affected endpoints:

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

Added

Add contacts list endpoint

Products: Contacts

Scope: API + SDKs

• What's new
  Adds a paginated endpoint to list workspace address book contacts with filtering by name, type, tags, access control, container, and archive status.

• Impact
  Customers can programmatically retrieve and filter their address book contacts through the API.

Affected endpoints:

1. List contacts

Add feeCurrency field for Tempo transactions (beta)

Products: Off exchanges, Transactions

Scope: API + SDKs

• What's new
  Adds an optional feeCurrency field to the transaction request schema, allowing users to specify which asset to use for paying network fees on Tempo-based transactions.

• Impact
  Customers using Tempo can now control which asset pays transaction fees.

Affected endpoints:

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

Add AMOUNT_ABOVE_MAXIMUM failure reason

Products: Trading (Beta)

Scope: API + SDKs

• What's new
  Adds a new enum value to indicate when a trading operation fails because the requested amount exceeds the maximum allowed limit.

• Impact
  Customers can now programmatically detect and handle amount-too-large errors in trading operations.

Affected endpoints:

1. Create an order
2. Get order details

---

[github-actions]

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