Generated SDK #2747190960 (major) - #150
Merged
sdk-generation-automation[bot] merged 1 commit intoAug 10, 2026
Merged
Conversation
Contributor
|
We've received your request. Thanks for your patience. (Note that this SDK code is auto generated) |
sdk-generation-automation
Bot
deleted the
fireblocks-api-spec/generated/2747190960
branch
August 10, 2026 11:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog
2026-08-10
Breaking Change
Make
ContractAttributesfields optionalProducts: Contract Templates
Scope: API + SDKs
What's new
Removes the required constraint from
useCases,standards, andauditorfields in theContractAttributesschema to match actual API behavior where these fields may be absent for non-EVM templates.Impact
SDK-generated types for these fields change from required/non-nullable to optional/nullable, requiring code updates where these fields are accessed.
Affected endpoints:
Changed
Expand
TravelRuleVASPresponse schema documentationProducts: Travel Rule
Scope: API + SDKs
What's new
Documents additional fields returned by the Travel Rule VASP endpoints, including GLEIF registry data, compliance phases, and regulatory status. Also clarifies
fieldsparameter behavior and notes that unrecognized fields should be ignored.Impact
Customers can now use the full set of VASP fields returned by the API.
Affected endpoints: