Generated SDK #9461 (major) #126
Open
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-02-05
Breaking Change
Change
tagfield type fromstringtobooleaninWalletAssetschemaAffected namespaces: Internal wallets
What's new
The
tagfield in theWalletAssetschema has been changed from a string type to a boolean type, affecting internal wallet asset endpoints. This change aligns the field type with its intended boolean usage pattern.Impact
Integrations consuming internal wallet asset responses must update their data models to handle the
tagfield as a boolean instead of a string. Existing string values will need to be converted to boolean equivalents during migration.Added
Add
DELETEendpoint for webhook notificationsAffected namespaces: Webhooks V2
What's new
A new
DELETEoperation has been added to the/webhooks/{webhookId}/notifications/{notificationId}endpoint, allowing customers to delete specific webhook notifications by ID. This provides better control over notification management and cleanup.Impact
Customers can now programmatically delete webhook notifications using the new
deleteNotificationoperation, enabling more efficient notification lifecycle management.