Generated SDK #2829319317 (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]

Your request is important to us. We will look into it shortly. (Note that this SDK code is auto generated)

[semgrep-code-fireblocks]

Semgrep identified an issue in your code:
package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.410.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

To resolve this comment:

🔧 No guidance has been designated for this issue. Fix according to your organization's approved methods.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by block-public-registry-refs-in-package-lock.

_{You can view more details about this finding in the Semgrep AppSec Platform.}

[semgrep-code-fireblocks]

Semgrep identified an issue in your code:
package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.11.15.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

To resolve this comment:

✨ Commit fix suggestion

Suggested change

	"resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.11.15.tgz",
	"resolved": "https://artifactory.example.com/api/npm/<VERIFIED_VALUE_REQUIRED>/baseline-browser-mapping/-/baseline-browser-mapping-2.11.15.tgz",

View step-by-step instructions

1. Configure the project’s .npmrc to use the approved internal JFrog/Artifactory npm registry, replacing the placeholder with the registry URL provided by your organization: registry=https://artifactory.example.com/api/npm/<repository>/.
2. Configure registry authentication through your approved credential mechanism, such as an environment variable or npm-supported token configuration; do not place credentials directly in the repository.
3. Remove the existing dependency installation and lockfile so npm does not retain public registry URLs: $ rm -rf node_modules package-lock.json.
4. Reinstall dependencies using the configured internal registry: $ npm install.
5. Confirm the regenerated package-lock.json resolves packages through the approved Artifactory registry and no longer contains https://registry.npmjs.org/ or another public registry URL.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by block-public-registry-refs-in-package-lock.

_{You can view more details about this finding in the Semgrep AppSec Platform.}