Generated SDK #5347 (major)#139
Merged
Merged
Conversation
Contributor
|
We've received your request. Thanks for your patience. (Note that this SDK code is auto generated) |
eranfireblocks
approved these changes
Jun 28, 2026
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-06-28
Breaking Change
Restructure Reports API response schemas (beta)
Products: Reports (Beta)
Scope: API + SDKs
What's new
Introduces a base report job schema and separates list responses from detail responses, removing short-lived download links from list items.
Impact
Customers must call the individual report endpoint to obtain download URLs instead of getting them from list responses.
Affected endpoints:
Update
ConnectedAccountErrorResponserequired fieldsProducts: Connected Accounts (Beta)
Scope: API + SDKs
What's new
Changes required fields from
errorMessage/errorCodetomessage/codewhile keeping legacy fields as optional.Impact
Customers must update error handling to use the new
messageandcodefields.Affected endpoints:
Relocate
participantsIdentificationPolicyto endpoint levelProducts: Trading (Beta)
Scope: API + SDKs
What's new
Moves the
participantsIdentificationPolicyproperty from the manifest root to individual endpoint configurations (order, quote, rate), enabling per-endpoint KYC/AML policy definitions.Impact
Customers must now read identification policies from endpoint-specific locations instead of the manifest root.
Affected endpoints:
Restructure Reports API response schemas (beta)
Products: Reports (Beta)
Scope: API + SDKs
What's new
Introduces a base report job schema and separates list responses from detail responses, removing short-lived download links from list items.
Impact
Customers must call the individual report endpoint to obtain download URLs instead of getting them from list responses.
Affected endpoints:
Update PayID schema field requirements
Products: External wallets
Scope: API + SDKs
What's new
Makes the
bsbfield required in PayID payment info and makesaccountNumberoptional in PayID address to align with current payment processing requirements.Impact
Customers must now provide the
bsbfield when creating PayID whitelist addresses.Affected endpoints:
Rename
verifiedfield toleiDatain Address RegistryProducts: Compliance
Scope: API + SDKs
What's new
Renames the
verifiedfield toleiDatain the Address Registry legal entity schema to better indicate LEI data availability.Impact
Existing integrations must update from
verifiedtoleiDatawhen parsing legal entity responses.Affected endpoints:
Add
vaultAccountIdanduserIdto Earn action responseProducts: Earn (Beta)
Scope: API + SDKs
What's new
Adds required
vaultAccountIdanduserIdfields to the Earn GetActionResponse schema, identifying which vault account and user executed each action.Impact
Customers can now see which vault account and user initiated each Earn action.
Affected endpoints:
Add Binance support to connected accounts allowlist | Add metadata envelope to allowlist entry response
Products: Connected Accounts (Beta)
Scope: API + SDKs
What's new
Connected accounts allowlist endpoints now support Binance accounts in addition to CoinbaseExchange. The allowlist entry endpoint now returns a response envelope containing both the entry data and account-level allowlist sync metadata.
Impact
Customers can use allowlist endpoints with Binance connected accounts. Customers receive additional sync metadata when retrieving individual allowlist entries.
Affected endpoints:
Restructure
PolicyMetadataas map keyed by policy typeProducts: Policy Editor V2 (Beta)
Scope: API + SDKs
What's new
Restructures the
PolicyMetadataschema from a flat object to a dictionary keyed by policy type, allowing metadata for multiple policies in a single response.Impact
Existing integrations parsing
PolicyMetadatamust update to handle the new map structure instead of direct properties.Affected endpoints:
Rename
vouttoindexin UTXO schemasProducts: Off exchanges, Transactions
Scope: API + SDKs
What's new
Renames the
voutfield toindexacross UTXO API schemas to align withlistUnspentand legacy input selection naming conventions.Impact
Beta customers using UTXO selection or identifier APIs must update requests to use
indexinstead ofvout.Affected endpoints:
Rename
vouttoindexin UTXO schemasProducts: UTXO Management (Beta)
Scope: API + SDKs
What's new
Renames the
voutfield toindexacross UTXO API schemas to align withlistUnspentand legacy input selection naming conventions.Impact
Beta customers using UTXO selection or identifier APIs must update requests to use
indexinstead ofvout.Affected endpoints:
Align
Exposureschema with vault allocation sliceProducts: Earn (Beta)
Scope: API + SDKs
What's new
Renames the
assetAddressfield toaddressand addsdecimals,assetId, andamountUsdfields to provide richer exposure data. AddsexposureTypeenum to describe what exposure rows represent and increases the exposure array limit from 10 to 20 items.Impact
Customers reading exposure data must update to use
addressinstead ofassetAddress.Affected endpoints:
Relocate
participantsIdentificationPolicyto endpoint levelProducts: Trading (Beta)
Scope: API + SDKs
What's new
Moves the
participantsIdentificationPolicyproperty from the manifest root to individual endpoint configurations (order, quote, rate), enabling per-endpoint KYC/AML policy definitions.Impact
Customers must now read identification policies from endpoint-specific locations instead of the manifest root.
Affected endpoints:
Remove Tags cancel approval request endpoint
Products: Tags
Scope: API + SDKs
What's new
Removes the endpoint to cancel an approval request for Tags, which was previously used to cancel pending approval requests by ID.
Impact
Customers can no longer cancel tag approval requests via API.
Affected endpoints:
Added
Add connected account creation endpoint (beta)
Products: Connected Accounts (Beta)
Scope: API + SDKs
What's new
Adds a beta endpoint to create connected accounts with RSA-encrypted credentials for exchange integrations.
Impact
Customers can programmatically create connected accounts using encrypted credentials.
Affected endpoints:
Add
rewardsBreakdownto Solana staking positionsProducts: Staking
Scope: API + SDKs
What's new
Adds a
rewardsBreakdownobject to Solana blockchain data containing issuance rewards, MEV rewards, and last sync timestamp.Impact
Customers can now view detailed breakdowns of staking rewards for Solana positions.
Affected endpoints:
Add async Reports API endpoints (beta)
Products: Reports (Beta)
Scope: API + SDKs
What's new
Adds beta endpoints to create and list asynchronous report jobs with pagination, filtering, and sorting capabilities.
Impact
Customers can generate and retrieve reports asynchronously through the API.
Affected endpoints:
Add account holder address fields to payment schemas
Products: External wallets
Scope: API + SDKs
What's new
Adds optional address fields (
accountHolderCity,accountHolderCountry,accountHolderPostalCode) to CHAPS and SEPA payment info schemas for enhanced address collection.Impact
Customers can now provide more detailed account holder address information when creating whitelist addresses.
Affected endpoints:
Add delete legal entity endpoint
Products: Compliance
Scope: API + SDKs
What's new
Adds a delete endpoint for legal entities that revokes the registration by changing its status to REVOKED. Only Admin and Non-Signing Admin roles can use this endpoint.
Impact
Customers can now programmatically revoke legal entity registrations through the API.
Affected endpoints:
Add
namefield to bulk vault account job statusProducts: Vaults
Scope: API + SDKs
What's new
Documents the vault account
namefield in the bulk vault account creation job status response, and fixes thestatusenum values to match actual API behavior.Impact
Customers can now see the vault account name in bulk creation job status responses.
Affected endpoints:
Add accrued
yieldfield to earn positionProducts: Earn (Beta)
Scope: API + SDKs
What's new
Adds an optional
yieldfield to thePositionschema representing accrued yield in principal token units as a decimal string, currently populated for Morpho positions only.Impact
Customers can now read accrued yield directly from position data for supported earn positions.
Affected endpoints:
Add
tagsfield to transaction responsesProducts: Transactions
Scope: API + SDKs
What's new
Adds a
tagsarray field to transaction source and destination responses, exposing policy engine-evaluated tags with up to 20 tags per transaction endpoint.Impact
Customers can view tags assigned by the policy engine on transaction sources and destinations.
Affected endpoints:
Add metadata envelope to allowlist entry response
Products: Connected Accounts (Beta)
Scope: API + SDKs
What's new
The allowlist entry endpoint now returns a response envelope containing both the entry data and account-level allowlist sync metadata.
Impact
Customers receive additional sync metadata when retrieving individual allowlist entries.
Affected endpoints:
Add
requiresReasonForPaymentfield to provider manifestProducts: Trading (Beta)
Scope: API + SDKs
What's new
Adds a boolean field to the provider manifest indicating when reason for payment information is required for compliance and reporting purposes.
Impact
Customers can check the provider manifest to determine if reason for payment is required before creating orders.
Affected endpoints:
Restructure
PolicyMetadataas map keyed by policy typeProducts: Policy Editor V2 (Beta)
Scope: API + SDKs
What's new
Restructures the
PolicyMetadataschema from a flat object to a dictionary keyed by policy type, allowing metadata for multiple policies in a single response.Impact
Existing integrations parsing
PolicyMetadatamust update to handle the new map structure instead of direct properties.Affected endpoints:
Add API user pairing token endpoint
Products: Api User
Scope: API + SDKs
What's new
Adds an endpoint to issue device pairing tokens for API users in pending activation status, available only to Owner, Admin, and Non-Signing Admin roles.
Impact
Customers can programmatically generate device pairing tokens for API users awaiting device setup.
Affected endpoints:
Add Reports API endpoints (beta)
Products: Reports (Beta)
Scope: API + SDKs
What's new
Adds beta endpoints to create and list asynchronous report jobs. Reports can be filtered by status and type, with paginated responses.
Impact
Customers can generate and manage downloadable reports programmatically through the API.
Affected endpoints:
Changed
Add
rewardsBreakdownto Solana staking positionsProducts: Staking
Scope: API + SDKs
What's new
Adds a
rewardsBreakdownobject to Solana blockchain data containing issuance rewards, MEV rewards, and last sync timestamp.Impact
Customers can now view detailed breakdowns of staking rewards for Solana positions.
Affected endpoints:
Policy Editor V2 is now generally available
Products: Policy Editor V2
Scope: API + SDKs
What's new
Removes the beta designation from Policy Editor V2 endpoints, indicating the feature is now production-ready.
Impact
Customers can use Policy Editor V2 endpoints with confidence as a stable, production feature.
Affected endpoints:
Update PayID schema field requirements
Products: Trading (Beta)
Scope: API + SDKs
What's new
Makes the
bsbfield required in PayID payment info and makesaccountNumberoptional in PayID address to align with current payment processing requirements.Impact
Customers now have more flexibility when providing PayID address information.
Affected endpoints:
Update
SourceOfFundsschema descriptionProducts: Trading (Beta)
Scope: API + SDKs
What's new
Clarifies that source of funds information should be provided when the provider manifest indicates it is required, removing specific provider references.
Impact
Customers get clearer guidance on when to provide source of funds information.
Affected endpoints: