Improved
Improved Subaccount Transactions with Staking and Delegation Reward Types
Improved: Added two new transaction types,STAKING_REWARD and DELEGATION_REWARD, to provide more detailed transaction information for subaccounts involved in staking.Category: SubaccountsEndpoints Changed:GET /subaccounts/transactions: Now supports filtering and returns the newSTAKING_REWARDandDELEGATION_REWARDtransaction types.GET /subaccounts/transactions/{transactionsIds}: ResponsetransactionTypefield now includes the new reward types.GET /subaccounts/transactions/allocations: ResponsetransactionTypefield now includes the new reward types.
transactionType field in responses may now include STAKING_REWARD and DELEGATION_REWARD, and the types query parameter on GET /subaccounts/transactions now supports filtering by these new values, enabling more granular tracking of staking-related activity.Example:Improved
Improved Rejection Reason for FillOrKill Trading Orders
Improved: Added theInvalidCurrencyForFOK enum value to the rejectReason field in the responses for several trading endpoints.Category: TradingEndpoints Changed:POST /trading/order: ResponserejectReasonnow includesInvalidCurrencyForFOK.POST /trading/async-order: ResponserejectReasonnow includesInvalidCurrencyForFOK.POST /trading/async-order/cancel: ResponserejectReasonnow includesInvalidCurrencyForFOK.
Improved
Improved Staking Requests with Asset-Specific Parameters
Improved: The staking request endpoint now supports specific configuration parameters for different assets; theparameters field in the request body is now a structured object.Category: TransactionsEndpoint Changed:POST /transactions/stake: Theparametersfield now accepts a structured object for asset-specific configurations, such asSOLandETHstaking parameters.
Added
Added Asset-Specific Staking Parameters
Added a newparameters object to the request body for creating stake requests, allowing for asset-specific configurations.Category: TransactionsEndpoint Changed:POST /transactions/stake: Request body now accepts aparametersobject supportingstakingProvider(e.g.FIGMENT,BLOCKDAEMON),stakingProviderAddress,stakingPositionId, andvalidatorType(e.g.0x01for Pre-Pectra,0x02for Post-Pectra).
Added
Added Talos as a Price Source Provider for Collateral Management
AddedTALOS as a supported price source provider for Collateral Management.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/exposures: ThepriceSourceProviderfield withinassetTrackingConfignow acceptsTALOSas a valid enum value.POST /collateral_management/packages: ThepriceSourceProviderfield withincollateralAssetsConfignow acceptsTALOSas a valid enum value.
TALOS as the provider for consolidating pricing data when creating new collateral exposures and packages.Improved
Improved Stablecoin Conversion Field Descriptions
Improved: Clarified the descriptions for thesourceAssetType and destinationAssetType fields to provide clearer guidance for issuance and redemption operations.Category: StablecoinsEndpoint Changed:POST /stablecoins/conversion: The description forsourceAssetTypenow states that for issuance the value must beUSD, and for redemptions it must be the asset being redeemed; the description fordestinationAssetTypenow states that for issuance the value must be the stablecoin asset, and for redemptions it must beUSD.
Improved
Improved Price Source Configuration for Collateral Management
Improved: Introduced apriceSourceProvider field to separate the pricing service provider from the underlying price source, and removed the KAMINO enum value from the priceSource field.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: AddedpriceSourceProviderto objects withincollateralAssetsConfig; removedKAMINOfrompriceSource.POST /collateral_management/exposures: AddedpriceSourceProvidertoassetTrackingConfig; removedKAMINOfrompriceSource.
KAMINO is now specified via the new optional priceSourceProvider field instead of priceSource.Improved
Improved Trading Statuses and Tax Tagging Responses
Improved: Added two new trading trade statuses and updated the response status code for asynchronous tax tagging operations.Category: Trading, TaxEndpoints Changed:POST /trading/quote/accept:tradeStatusenum now includesPENDINGALLOCATIONandALLOCATED.GET /trading/trades:tradeStatusenum now includesPENDINGALLOCATIONandALLOCATED.GET /trading/trades/{tradeId}:tradeStatusenum now includesPENDINGALLOCATIONandALLOCATED.GET /trading/settlements/{settlementId}/trades:tradeStatusenum now includesPENDINGALLOCATIONandALLOCATED.POST /tax/transaction/{transactionId}/tag: Now returns202 Acceptedto indicate the request is being processed rather than immediately complete.DELETE /tax/transaction/{transactionId}/tag: Now returns202 Acceptedto indicate the request is being processed rather than immediately complete.
PENDINGALLOCATION means a trade is awaiting client allocation, ALLOCATED means it is fully allocated). The tax tagging endpoints now more accurately reflect asynchronous processing with a 202 Accepted status rather than implying immediate completion.Improved
Improved Collateral Management Price Sourcing with KAMINO
Improved: AddedKAMINO as a new enum value for the priceSource field when creating collateral packages and exposures.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceSourcefield withincollateralAssetsConfignow acceptsKAMINO.POST /collateral_management/exposures: ThepriceSourcefield withinassetTrackingConfignow acceptsKAMINO.
KAMINO as the source for price information when creating new collateral packages and exposures.Added
Added Price Staleness Configuration for Collateral Packages
Added an optionalmaxStalenessMinutes field to the request body for creating collateral packages, allowing configuration of the maximum age of an asset’s price before it is considered stale.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/packages: Each object withincollateralAssetsConfignow accepts an optional integermaxStalenessMinutesfield.
maxStalenessMinutes is not provided, the system defaults to 3 minutes.Example:Improved
Improved Vesting Balances Response with Asset Context
Improved: The response for getting vesting balances now includesexternalTokenId and networkId for added asset context.Category: VestingEndpoint Changed:GET /vesting/balances/{allocationId}: Thebalanceobject in the response now contains two new required fields:externalTokenId(the asset ID assigned by the external provider) andnetworkId(the blockchain network identifier).
Improved
Improved Trading Status Clarity and Added Tax Transaction Tagging
Improved: Added new endpoints for tagging tax transactions and expanded and clarified trading status fields.Category: Tax, TradingEndpoints Added:POST /tax/transaction/{transactionId}/tag: Adds a tag to a transaction for tax purposes.DELETE /tax/transaction/{transactionId}/tag: Removes a tag from a transaction.
POST /trading/quote:quoteStatusdescription clarified.POST /trading/quote/accept:quoteStatusandtradeStatusdescriptions clarified;tradeStatusnow includesPENDINGALLOCATIONandALLOCATED.GET /trading/trades:tradeStatusdescription clarified and expanded.GET /trading/trades/{tradeId}:tradeStatusdescription clarified and expanded.GET /trading/settlements/{settlementId}/trades:tradeStatusdescription clarified and expanded.
PENDINGALLOCATION and ALLOCATED trading statuses, along with clearer field descriptions, offers better visibility into the post-execution allocation process.Added
Added stakeholderId Parameter to Vesting Balances Endpoint
Added an optionalstakeholderId query parameter to the vesting balances endpoint.Category: VestingEndpoint Changed:GET /vesting/balances/{allocationId}: New optionalstakeholderIdquery parameter can be used to retrieve wallet information for a stakeholder.
Improved
Improved API Key Permissions with FIAT_BANKING
Improved: Added theFIAT_BANKING permission type.Category: API KeyEndpoint Changed:GET /apikey: Response may now includeFIAT_BANKINGas a value in thepermissionfield within thepermissionsarray.
permissions array should be updated to handle the new FIAT_BANKING enum value.Example:Improved
Improved Parameter Descriptions for Delegation Addresses
Improved: Updated the descriptions for parameters on the delegation addresses endpoint to provide better clarity.Category: TransactionsEndpoint Changed:GET /delegation-addresses/{assetType}: Descriptions for theassetType,afterId, andlimitparameters have been improved.
Added
Added Endpoint for Listing Delegation Addresses
Added a new endpoint to list supported delegation addresses for staking.Category: TransactionsEndpoint Added:GET /delegation-addresses/{assetType}: Retrieves a list of supported delegation addresses for a specific asset type.
Improved
Improved Delegation Address Details with Validator Information
Improved: The delegation addresses endpoint now includes additional details about the validator for each delegation address.Category: Delegation AddressesEndpoint Changed:GET /delegation-addresses/{assetType}: Each address object in thedataarray now includes two new required fields:anchorageValidator(boolean) andvalidatorType(string).
Improved
Improved Collect Requests by Making Amount Optional
Improved: Theamount field in the request body for creating a collect request is now optional.Category: TransactionsEndpoint Changed:POST /transactions/collect: Theamountproperty is no longer required.
amount field to collect the full inactive unstaked amount for a given staking position; if not specified, the request defaults to collecting the entire available amount.Added
Added Endpoint to List Delegation Addresses
Added a new endpoint to list supported delegation addresses for a given asset type.Category: AddressesEndpoint Added:GET /delegation-addresses/{assetType}: Lists supported delegation addresses for the specified asset type.
Added
Added Endpoint to Update Customer Onboarding Applications
Added the ability to update existing customer onboarding applications before they are submitted for review.Category: OnboardingEndpoint Added:PUT /onboarding/customers/{customerId}: Updates the data of an existing customer onboarding application by accepting anentriesarray of key-value pairs.
Improved
Improved Collateral Exposures by Making Weight Optional
Improved: Theweight field within the assetTrackingConfig object is now optional when creating a new collateral exposure.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/exposures: Theweightfield inassetTrackingConfigis no longer required.
Improved
Improved Trading Statuses and Staking Full-Amount Operations
Improved: Added new trading statuses and enhanced unstake and collect operations with a full-amount option.Category: Trading, TransactionsEndpoints Changed:POST /trading/quote:quoteStatusenum updated to consistently reflect the quote lifecycle (OPEN,REJECTED,EXECUTED).POST /trading/quote/accept:tradeStatusnow includesPENDINGALLOCATIONandALLOCATED.GET /trading/trades:tradeStatusnow includesPENDINGALLOCATIONandALLOCATED.GET /trading/trades/{tradeId}:tradeStatusnow includesPENDINGALLOCATIONandALLOCATED.GET /trading/settlements/{settlementId}/trades:tradeStatusnow includesPENDINGALLOCATIONandALLOCATED.POST /transactions/unstake: TheisFullAmountparameter description clarified to indicate it overrides any provided amount.POST /transactions/collect: NewisFullAmountboolean parameter added.
isFullAmount: true for unstake and collect operations to process the full available balance, removing the need to first query for the exact amount.Improved
Improved Staking Position Data and Trading Status Descriptions
Improved: Added theinactiveStakedAmount field to staking position responses and clarified the descriptions for trading status fields.Category: Wallets, TradingEndpoints Changed:GET /wallets/{walletId}/staking/positions: Response now includes the numericinactiveStakedAmountfield (excluding units).POST /trading/quote:quoteStatusdescription clarified.POST /trading/quote/accept:quoteStatusandtradeStatusdescriptions clarified, including thePENDINGALLOCATIONandALLOCATEDstates.GET /trading/trades:tradeStatusdescription clarified.GET /trading/trades/{tradeId}:tradeStatusdescription clarified.GET /trading/settlements/{settlementId}/trades:tradeStatusdescription clarified.
Improved
Improved Tax Form Responses with Additional Details
Improved: Enhanced tax form responses with additional details for each tax form.Category: TaxEndpoints Changed:GET /tax/subaccounts/{subaccountId}/forms: Each form object now includesid,createdDate,year,revision,revisionType, andisFiledfields.GET /tax/clients/{customerId}/forms: Each form object now includesid,createdDate,year,revision,revisionType, andisFiledfields.
Improved
Improved Descriptions for Creating Trusted Destinations
Improved: Updated the descriptions for fields in the request body to provide better clarity.Category: Trusted DestinationsEndpoint Changed:POST /trusted_destinations: Descriptions for thetrustedDestinationsarray and thenameproperty within array items have been improved.
Improved
Improved Collect Request Body with Source and Idempotency
Improved: The request body for creating a collect request now includessource, description, and an idempotency key.Category: TransactionsEndpoint Changed:POST /transactions/collect: Request body now requires asourceobject specifying the wallet to collect from, and adds optionaldescriptionandidempotentIdfields. The201 Createdresponse now returns anapplication/jsonpayload.
source field is now required. Clients using this endpoint must update their integration to include the source object.Improved
Improved Error Handling for Asynchronous Orders
Improved: Added theInvalidAccountsInAllocation reject reason for asynchronous orders that fail due to subaccount allocation issues.Category: TradingEndpoints Changed:POST /trading/async-order: ResponserejectReasonnow includesInvalidAccountsInAllocation.POST /trading/async-order/cancel: ResponserejectReasonnow includesInvalidAccountsInAllocation.
Improved
Improved Stablecoin Conversion Creation Response
Improved: The201 Created response for creating a stablecoin conversion now supports a new authorization workflow.Category: StablecoinsEndpoint Changed:POST /stablecoins/conversion: The response now returns a requiredauthorizationOperationIdinstead ofconversionId;conversionIdis now optional in the response.
authorizationOperationId to track the authorization status of the stablecoin conversion request.Improved
Improved Collateral Management with Interest Paydown and Accrual Actions
Improved: AddedINTEREST_PAYDOWN and INTEREST_ACCRUAL as new valid actions for Collateral Management operations.Category: Collateral ManagementEndpoints Changed:PATCH /collateral_management/operations/{operationId}:actionfield now supportsINTEREST_PAYDOWNandINTEREST_ACCRUAL.POST /collateral_management/operations:actionfield now supportsINTEREST_PAYDOWNandINTEREST_ACCRUAL.GET /collateral_management/operations:actionfield in responses now supportsINTEREST_PAYDOWNandINTEREST_ACCRUAL.
Added
Added Endpoints for Retrieving Account Statements
Added new endpoints for listing and downloading account statements.Category: StatementsEndpoints Added:GET /statement-types: Lists available statement types.GET /statements: Lists generated statements for your account.GET /statements/{statementId}: Gets details for a specific statement by its ID.GET /statements/{statementId}/download: Downloads a specific statement file.
Added
Added Webhook Notifications for Real-Time Event Updates
Added support for Webhook Notifications to receive real-time updates on account activity.Category: Webhook NotificationsEndpoints Added:GET /webhook/validation-key: Retrieves the key used to validate webhook payload signatures.GET /webhook/event-types: Lists all available event types you can subscribe to.POST /webhook/endpoints: Creates a new webhook endpoint.GET /webhook/endpoints: Lists your webhook endpoints.GET /webhook/endpoints/{endpointId}: Gets a specific webhook endpoint.PATCH /webhook/endpoints/{endpointId}: Updates a webhook endpoint.POST /webhook/endpoints/{endpointId}/subscriptions: Subscribes an endpoint to an event type.GET /webhook/endpoints/{endpointId}/subscriptions: Lists an endpoint’s event subscriptions.DELETE /webhook/endpoints/{endpointId}/subscriptions/{eventTypeId}: Removes an endpoint’s subscription to an event type.
withdrawal.initiated or transfer.completed, eliminating the need for polling. An API key with the Configure Webhooks permission is required to use these endpoints.Example:Improved
Improved Trading Orders with Subaccount Allocation Details
Improved: Trading endpoints now support and return subaccount allocation details.Category: TradingEndpoints Changed:POST /trading/async-order: Request body now accepts anallocationarray specifying how the order should be allocated across subaccounts.POST /trading/async-order/cancel: Response now includes a detailedallocationobject.POST /trading/order: Response now includes a detailedallocationobject.GET /trading/orders: Response now includes a detailedallocationobject.GET /trading/orders/{orderId}: Response now includes a detailedallocationobject.
allocation object includes subaccountId, quantity, fee, and executionId.Example:Improved
Improved Gas Station Fee Option for Transfers and Withdrawals
Improved: Clarified theuseGasStation parameter for handling network fees on transfers and withdrawals.Category: Transactions, TransfersEndpoints Changed:POST /transactions/withdrawal: The optional booleanuseGasStationfield is now more clearly documented.POST /transfers: The optional booleanuseGasStationfield is now more clearly documented.
useGasStation to true allows the Anchorage Digital gas station to pay for network fees, simplifying fee management for supported asset types and organizations. If the parameter is omitted, it defaults to false.Example:Added
Added Collect Endpoint and Improved Staking Operations
Added a new transaction type for collect requests and enhanced staking and unstaking requests with a full-amount option.Category: TransactionsEndpoint Added:POST /transactions/collect: Creates a collect request.
POST /transactions/stake: Request body now accepts an optional booleanisFullAmountfield.POST /transactions/unstake: Request body now accepts an optional booleanisFullAmountfield.
isFullAmount to true on stake and unstake requests performs the operation for the full available amount, removing the need for clients to manually specify the quantity.Added
Added LTV Rounding Precision to Collateral Package Creation
Added a newltvRoundingPrecision field for specifying the number of decimal places to round Loan-to-Value (LTV) ratios.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/packages: Request body now accepts an optionalltvRoundingPrecisionfield.
Improved
Improved Stablecoin Conversion Request Body
Improved: Standardized how amounts and idempotency are handled when creating a stablecoin conversion.Category: StablecoinsEndpoint Changed:POST /stablecoins/conversion: Removed the optionaldecimalAmountandidempotentIdfields; added required fieldsamount(string) andidempotencyKey(string).
amount and idempotencyKey.Example:Previous Request Structure:Improved
Improved Trading and Quote Status Descriptions
Improved: Updated thetradeStatus and quoteStatus fields across multiple Trading endpoints with more detailed descriptions and a comprehensive list of possible values.Category: TradingEndpoints Changed:POST /trading/quote:quoteStatusdescription expanded.POST /trading/quote/accept:tradeStatusandquoteStatusdescriptions expanded.GET /trading/settlements/{settlementId}/trades:tradeStatusdescription expanded.GET /trading/trades:tradeStatusdescription expanded.GET /trading/trades/{tradeId}:tradeStatusdescription expanded.
tradeStatus field now documents the following possible values: PENDING, REJECTED, CANCELED, EXECUTED, SETTLING, SETTLED, PENDINGALLOCATION, and ALLOCATED.Improved
Improved Trading API Documentation Clarity
Improved: Enhanced documentation for several Trading endpoints with clearer explanations, more detailed examples, and updated field descriptions.Category: TradingEndpoints Changed:GET /trading/accounts/{accountId}: Clarified404 Not Foundresponse description.POST /trading/async-order: Description clarity improvements.POST /trading/order: Description clarity improvements.GET /trading/pairs: Enhanced description of thereferenceDataobject.POST /trading/quote: Added comprehensive request body examples forBUY,SELL, andTWOWAYscenarios; clarifiedquoteStatusdescription.POST /trading/quote/accept: Improved description ofallowedSlippageandvaultID, including a detailed example of howallowedSlippagefunctions.GET /trading/settlements/{settlementId}/trades: ClarifiedtradeStatusandsettlementStatusdescriptions and the404 Not Foundresponse.GET /trading/trades: ClarifiedtradeStatusdescription.GET /trading/trades/{tradeId}: ClarifiedtradeStatusdescription.GET /trading/settlements: ClarifiedsettlementStatusdescription.GET /trading/settlements/{settlementId}: ClarifiedsettlementStatusdescription; updatedpricefield description to explain its composition and asynchronous availability.
Improved
Improved Async Order Rejection with OrderNotCancelable Reason
Improved: Added theOrderNotCancelable value to the rejectReason enum for asynchronous order responses.Category: TradingEndpoints Changed:POST /trading/async-order:rejectReasonnow includesOrderNotCancelable.POST /trading/async-order/cancel:rejectReasonnow includesOrderNotCancelable.
Improved
Improved Transaction Filtering with New Reward Types
Improved: Thetypes query parameter for listing transactions now supports more granular filtering by reward type.Category: TransactionsEndpoint Changed:GET /transactions: Thetypesquery parameter now acceptsDELEGATION_REWARD,STAKING_REWARD,RESTAKING_REWARD, andALLUVIAL_STAKING_REWARD.
Added
Added Atlas Settlement Network, Collateral Management, Stablecoins, Tax, Trusted Destinations, and Webhook Endpoints
Added a broad set of new endpoints spanning the Atlas Settlement Network, Collateral Management, Stablecoins, Tax Reporting, Trusted Destinations, and Webhook Notifications, alongside significant enhancements to core custody operations for vaults, wallets, transactions, and transfers.Category: Atlas Settlement Network, Collateral Management, Stablecoins, Tax, Trusted Destinations, Webhook Notifications, CustodyEndpoints Added:GET /atlas/directory/counterparties: Lists counterparties on the Atlas Settlement Network.GET /atlas/directory/counterparties/{counterpartyId}: Gets a specific counterparty.GET /atlas/directory/participants: Lists participants on the Atlas Settlement Network.POST /atlas/settlements: Proposes a new settlement.GET /atlas/settlements: Lists settlements.GET /atlas/settlements/{settlementId}: Gets a specific settlement.POST /atlas/settlements/{settlementId}/accept: Accepts a settlement proposal.POST /atlas/settlements/{settlementId}/authorize: Authorizes a settlement.POST /atlas/settlements/{settlementId}/reject: Rejects a settlement proposal.GET /collateral_management/exposures: Lists collateral exposures.POST /collateral_management/exposures: Creates a collateral exposure.GET /collateral_management/operations: Lists collateral operations.POST /collateral_management/operations: Creates a collateral operation.PATCH /collateral_management/operations/{operationId}: Updates a collateral operation.GET /collateral_management/packages: Lists collateral packages.POST /collateral_management/packages: Creates a collateral package.PATCH /collateral_management/packages/{packageId}: Updates a collateral package.POST /stablecoins/conversion: Creates stablecoin conversions, including issuance and redemption.GET /tax/inventory/summary/{subaccountId},PATCH /tax/transaction/{transactionId},GET /tax/clients/{customerId}/forms, and more: A full suite of endpoints to fetch tax transactions, gains, inventory, and forms, and to update cost basis.GET /trusted_destinations,POST /trusted_destinations,DELETE /trusted_destinations/{creationRequestId}/cancel, and more: Create, list, and manage the lifecycle of trusted destinations.GET /webhook/endpoints: Lists webhook endpoints.POST /webhook/endpoints: Creates a webhook endpoint.GET /webhook/endpoints/{endpointId}: Gets a webhook endpoint.PATCH /webhook/endpoints/{endpointId}: Updates a webhook endpoint.GET /webhook/endpoints/{endpointId}/subscriptions: Lists an endpoint’s subscriptions.POST /webhook/endpoints/{endpointId}/subscriptions: Subscribes an endpoint to an event type.DELETE /webhook/endpoints/{endpointId}/subscriptions/{eventTypeId}: Removes an event subscription.GET /webhook/event-types: Lists available webhook event types.GET /webhook/validation-key: Retrieves the webhook payload validation key.
GET /vaults,POST /vaults/{vaultId}/wallets,GET /wallets,GET /wallets/{walletId}/staking/positions,GET /wallets/{walletId}/staking/rewards: Expanded for comprehensive listing and creation, including access to staking data.GET /vaults/{vaultId}/addresses,POST /wallets/{walletId}/addresses: Expanded to list and provision new deposit addresses.POST /transactions/stake,POST /transactions/unstake,POST /transactions/withdrawal: Expanded to initiate staking and withdrawal operations.POST /transfers,GET /transfers,DELETE /transfers/{transferId}: Expanded to create, list, and cancel automated asset transfers.
Added
Added 422 Error Response for Collateral Exposure Creation
Added a422 Unprocessable Entity error response to the endpoint for creating a new collateral exposure.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/exposures: May now return a422 Unprocessable Entityresponse when a request is syntactically correct but cannot be processed due to semantic or business logic errors.
422 status code for this endpoint.Added
Added Endpoint for Stablecoin Conversions
Added a new endpoint to enable programmatic conversion between stablecoins.Category: Stablecoin ConversionsEndpoint Added:POST /stablecoins/conversion: Creates a stablecoin conversion.
Added
Added Trusted Destination Support for Transfers and Withdrawals
Added support forTRUSTED_DESTINATION as a valid destination type, allowing you to specify a pre-approved trusted destination when creating transfers and withdrawals.Category: Transfers, TransactionsEndpoints Changed:POST /transfers:destination.typenow acceptsTRUSTED_DESTINATION.POST /transactions/withdrawal:destination.typenow acceptsTRUSTED_DESTINATION.GET /transfers: Response now reflects theTRUSTED_DESTINATIONdestination type.GET /transfers/{transferId}: Response now reflects theTRUSTED_DESTINATIONdestination type.
Improved
Improved Tax Inventory Response Field Casing
Improved: Updated theAverageUnitCost field to averageUnitCost in the tax inventory response for casing consistency.Category: TaxEndpoint Changed:GET /tax/inventory/{subaccountId}/{assetTypeId}: Response field renamed fromAverageUnitCosttoaverageUnitCost.
AverageUnitCost field must be updated to use the new averageUnitCost field name.Example:Previous Response Structure:Improved
Improved API Key Permissions and Signature Documentation
Improved: Added a new API key permission for converting stablecoins and clarified signature header documentation for staking endpoints.Category: API Key, TransactionsEndpoints Changed:GET /apikey: Responsepermissionsarray may now include the newCONVERT_STABLECOINSpermission.POST /transactions/stake:Api-Signatureheader documentation clarified.POST /transactions/unstake:Api-Signatureheader documentation clarified.
CONVERT_STABLECOINS permission may now appear in GET /apikey responses if enabled for the API key. The signature header documentation update is documentation-only and does not affect API functionality.Added
Added Wallet Search by Address
Added a newsearchByAddress query parameter to find wallets by a full or partial address they contain.Category: WalletsEndpoint Changed:GET /wallets: NewsearchByAddressquery parameter, requiring a minimum of 3 characters.
Added
Added Strategy Parameters to Trading Order Responses
Added astrategyParams object to trading order responses to provide more detail on strategy-based orders.Category: TradingEndpoints Changed:GET /trading/orders: Response now includes astrategyParamsobject containingtriggerPriceandendTimefor applicable order types.GET /trading/orders/{orderId}: Response now includes astrategyParamsobject containingtriggerPriceandendTimefor applicable order types.
Improved
Improved Error Handling for Collateral Package Creation
Improved: Added a new422 Unprocessable Entity response to provide more specific error feedback when creating a new collateral package.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/packages: May now return a422 Unprocessable Entityresponse.
422 Unprocessable Entity status code, which indicates the request syntax is correct but the server cannot process it due to semantic errors or failed business logic validation.Added
Added Endpoint to Cancel Trusted Destination Creation
Added a new endpoint to cancel a pending Trusted Destination creation request.Category: Trusted DestinationsEndpoint Added:DELETE /trusted_destinations/{creationRequestId}/cancel: Cancels a pending Trusted Destination creation request. ThecreationRequestIdcorresponds to theidempotentIdprovided in the initialPOST /trusted_destinationsrequest.
Improved
Improved Standardization of rejectReason Enum for Async Orders
Improved: Standardized therejectReason enum values for asynchronous trading orders to provide clearer, more consistent error codes.Category: TradingEndpoints Changed:POST /trading/async-order:rejectReasonenum standardized — removedErrInvalidLimitPriceForSell,ErrInvalidLimitPriceForBuy,ErrInvalidTriggerPrice, andErrInvalidLimitPrice; addedInvalidLimitPriceandInvalidTriggerPrice.POST /trading/async-order/cancel: SamerejectReasonenum changes as above.
rejectReason field for specific error reasons should update their logic to use the new enum values.Improved
Improved Async Order Rejection with ErrInvalidLimitPrice Reason
Improved: Added theErrInvalidLimitPrice enum value to the rejectReason field for async order endpoints.Category: TradingEndpoints Changed:POST /trading/async-order:rejectReasonnow includesErrInvalidLimitPrice.POST /trading/async-order/cancel:rejectReasonnow includesErrInvalidLimitPrice.
Improved
Improved Subaccount Balances with Detailed Entry Breakdown
Improved: Subaccount details responses now include a granular breakdown of balances via a newentries field.Category: SubaccountsEndpoints Changed:GET /subaccounts/customers/accounts: Each object in thebalancesarray now contains anentriesarray, with each entry providing anamountanddescriptionfor a component of the total balance (e.g., Posted, Pending).GET /subaccounts/customers/{customerId}/accounts: Sameentriesaddition to thebalancesarray.
Deprecated
Deprecated VAULT Resource Type for Transfers and Withdrawals
Deprecated: The use ofVAULT as a resource type for identifying the source and destination of funds. Users must specify a WALLET ID instead.Category: Transfers, Transactions, Vaults, WalletsEndpoints Changed:POST /transactions/withdrawal:source.type/destination.typeno longer acceptVAULT; useWALLET.POST /transfers:source.type/destination.typeno longer acceptVAULT; useWALLET.GET /transfers: Response reflects that wallet resourcetypeis alwaysWALLET.GET /transfers/{transferId}: Response reflects that wallet resourcetypeis alwaysWALLET.GET /vaults: Response reflects the deprecation.GET /vaults/{vaultId}: Response reflects the deprecation.GET /vaults/{vaultId}/wallets: Response reflects the deprecation.POST /vaults/{vaultId}/wallets: Response reflects the deprecation.GET /wallets: Response reflects that wallet resourcetypeis alwaysWALLET.GET /wallets/{walletId}: Response reflects that wallet resourcetypeis alwaysWALLET.
VAULT ID must be updated to use a specific WALLET ID; the previous behavior of defaulting to a vault’s default wallet is removed. This ensures all asset movements explicitly specify which wallet within a vault should be used.Example:Previous Request Structure:Improved
Improved Trusted Destinations Response Structure
Improved: The response for listing trusted destinations now provides more detailed information — theowners array has been replaced by a structured owner object, and new name and description fields have been added.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations:ownersarray replaced with anownerobject; addednameanddescriptionfields.
owners array must be updated to use the new owner object.Example:Previous Response Structure:Improved
Improved Async Order Parameters and Content Type
Improved: Changed the request body content type and clarified theparameters property for asynchronous orders.Category: TradingEndpoint Changed:POST /trading/async-order: Request body content type changed toapplication/json. Theparametersproperty is now specifically forSTOP_LOSS,STOP_LIMIT, andTAKE_PROFIT_LIMITorder types, including optionalendTimeand requiredtriggerPriceparameters.
parameters property and formalizes the request body content type.Improved
Improved Wallet Filtering Parameter Naming
Improved: Renamed theassetTypeId query parameter to assetType for wallet listing endpoints.Category: WalletsEndpoints Changed:GET /vaults/{vaultId}/wallets:assetTypeIdquery parameter replaced withassetType.GET /wallets:assetTypeIdquery parameter replaced withassetType.
assetTypeId to assetType.Added
Added networkId and assetTypeId Filters to Wallet Endpoints
AddednetworkId and assetTypeId query filters to the wallet listing endpoints.Category: WalletsEndpoints Changed:GET /vaults/{vaultId}/wallets: New optionalnetworkIdandassetTypeIdquery parameters filter results to wallets matching the given network or asset type.GET /wallets: New optionalnetworkIdandassetTypeIdquery parameters filter results to wallets matching the given network or asset type.
Added
Added Endpoint to Update Collateral Packages
Added a new endpoint to update an existing collateral package.Category: Collateral ManagementEndpoint Added:PATCH /collateral_management/packages/{packageId}: Updates an existing collateral package.
Added
Added RFQ Order Type to Trading Endpoints
AddedRFQ as a new order type on Trading endpoints.Category: TradingEndpoints Changed:GET /trading/orders:orderTypefield in responses now includesRFQas a possible value.GET /trading/orders/{orderId}:orderTypefield in responses now includesRFQas a possible value.
RFQ type.Added
Added Expired Status to Trusted Destinations Workflow
AddedExpired as a new status value in the Trusted Destination creation request workflow.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations/{creationRequestId}/status:statusfield may now returnExpired.
Expired indicates that the Trusted Destination creation request has expired.Added
Added Collateral Exposures Endpoint and Updated Collateral Packages
Added support for creating collateral exposures, and updated the request body for creating collateral packages.Category: Collateral ManagementEndpoint Added:POST /collateral_management/exposures: Creates a collateral exposure.
POST /collateral_management/packages: Removed the requiredinternalNameproperty; changed thecollateralAssetsConfigarray.
Added
Added internalName and priceStrategy to Collateral Package Creation
Added an optionalinternalName field and a required priceStrategy field to collateral package creation.Category: Collateral ManagementEndpoint Changed:POST /collateral_management/packages: Request body now accepts an optionalinternalName(string) for internal tracking, and requires apriceStrategy(string) field specifying the pricing strategy, withDEFAULTas a valid enum value.
Added
Added Collateral Package Creation and Improved Package Retrieval
Added a new endpoint to create collateral packages, and expanded the response for retrieving collateral packages with more detailed level configuration.Category: Collateral ManagementEndpoint Added:POST /collateral_management/packages: Creates a new collateral package.
GET /collateral_management/packages: TheacceleratedMarginCallandcriticalobjects now includereturnToLtvandwarningLtvproperties, with thecriticalobject now required; theactionenum for these objects now includesNONE,PARTIAL,FULL, andSWEEP. ThemarginCallobject addscurePeriod,curePeriodProtection, andtopUpTypeproperties with the same expandedactionenum. ThemarginReturnobject adds areturnToLtvproperty with anactionenum ofNONEandSWEEP.
Added
Added GAS_STATION Transaction Type
AddedGAS_STATION as a new transactionType enum value.Category: TransactionsEndpoints Changed:GET /transactions:transactionTypefield now includesGAS_STATION.GET /transactions/{transactionId}:transactionTypefield now includesGAS_STATION.
transactionType field in responses can now be GAS_STATION, representing funds received from the gas station to cover network fees, providing more granular information about transaction types.Added
Added Owners Field to Trusted Destinations Response
Added anowners field to the Trusted Destinations response.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations: Each object in thedataarray now includes anownersfield, an array of strings representing the owners of the trusted destination.
Added
Added REHYPE_IN and REHYPE_OUT Actions for Collateral Management
AddedREHYPE_IN and REHYPE_OUT as new valid actions for collateral package operations, and clarified the documentation for the action property.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/operations:actionfield now supportsREHYPE_INandREHYPE_OUT.PATCH /collateral_management/operations/{operationId}:actionfield now supportsREHYPE_INandREHYPE_OUT.GET /collateral_management/operations:actionfield in responses now supportsREHYPE_INandREHYPE_OUT.
REHYPE_IN and REHYPE_OUT operations do not change the balance of the collateral package used for LTV monitoring. The documentation for the action property was also clarified, noting that CLOSE_RETURN is not currently supported and that write operations for liquidations are also not supported.Improved
Improved Trusted Destination Status Granularity
Improved: Updated the possible values for thestatus property to provide more granularity into the Trusted Destination creation workflow.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations/{creationRequestId}/status:statusfield now returns one ofInitiated,Generating Docusign,Pending DocuSign Signature,Trusted Destination Operation In Progress,Needs Quorum Approval,Anchorage Risk Review,Linking Trusted Destination,Complete,Failed,Rejected, orCanceled.
Pending DocuSign Signature during the signature step, or Needs Quorum Approval while awaiting internal approvals.Added
Added Vesting Balances Endpoint
Added a new endpoint to get vesting balances for an allocation.Category: VestingEndpoint Added:GET /vesting/balances/{allocationId}: Retrieves vesting balances for a given allocation.
allocationId. For aggregate investor vesting balances, see unvestedUnstakeableBalance and unvestedBalance in any balance endpoint (e.g. GET /wallets).Added
Added Async Order Endpoint and Expanded Order Types
Added new endpoints to place and cancel asynchronous trading orders, and expanded the set of supported order types.Category: TradingEndpoints Added:POST /trading/async-order: Places an async order (Market or Limit; currently only FillOrKill is supported). One ofaccountIdorsubaccountIdmust be specified, but not both.POST /trading/async-order/cancel: Cancels an async order.
GET /trading/orders:orderTypenow includesSTOP_LIMIT,TAKE_PROFIT_LIMIT,STOP_LOSS,TWAP,VWAP,PEGGED,POV, andOTHER;orderStatusnow includesPENDING_CANCEL.GET /trading/orders/{orderId}:orderTypenow includesSTOP_LIMIT,TAKE_PROFIT_LIMIT,STOP_LOSS,TWAP,VWAP,PEGGED,POV, andOTHER.
PENDING_CANCEL status indicates that a cancellation request has been received for an async order.Improved
Improved Webhook Endpoints with Public Key Support
Improved: AddedpublicKey support across webhook endpoint management, and added a new API key permission for configuring webhooks.Category: Webhook Notifications, API KeyEndpoints Changed:GET /webhook/endpoints: Response now includes apublicKeyproperty for each endpoint.POST /webhook/endpoints: Request body now accepts an optionalpublicKeyfield.GET /webhook/endpoints/{endpointId}: Response now includes apublicKeyproperty.PATCH /webhook/endpoints/{endpointId}: Request body now accepts apublicKeyproperty, allowing it to be updated.GET /apikey:permissionsarray now supports a newCONFIGURE_WEBHOOKSpermission, which controls access to webhook configuration endpoints.
CONFIGURE_WEBHOOKS permission must be granted to an API key to create or manage webhook endpoints.Added
Added Trusted Destinations Status Endpoint
Added a new endpoint to track the status of a Trusted Destination creation request.Category: Trusted DestinationsEndpoint Added:GET /trusted_destinations/{creationRequestId}/status: Retrieves the status of a Trusted Destination creation request, using thecreationRequestIdpath parameter (the idempotent ID provided in the Create Trusted Destination request).
Added
Added Create Allocations Endpoint for Wealth Management
Added the ability to create new allocations between subaccounts of the same Program Customer.Category: SubaccountsEndpoint Added:POST /subaccounts/transactions/allocations: Creates new allocations between subaccounts of the same Program Customer. This is a transactional operation — either all allocations are created successfully, or none are. A maximum of 100 allocations and 10 unique assets per request are enforced. If allocations are successfully created, any relevant pending subaccount transactions are updated to reflect them.
Improved
Improved Withdrawal Requests with Trusted Destination AML Support
Improved: The withdrawal request endpoint now references Trusted Destination AML information directly, reducing the need to resubmit duplicate AML data, and adds support for Wealth Management subaccount withdrawals.Category: TransactionsEndpoint Changed:POST /transactions/withdrawal:beneficiaryanddestinationAML fields are now fully optional (not deprecated). A new optional boolean field,useTrustedDestinationAml(defaultfalse), lets the caller indicate the system should use the associated Trusted Destination’s AML information instead of resubmitting it. A newSUBACCOUNTsource type is supported, with originator information auto-populated for Wealth Management clients. For joint accounts,source.customerIdis now mandatory, and the AML questionnaire’spurposefield is now required.
useTrustedDestinationAml defaults to false, preserving prior behavior. No action is required unless you want to use the new field, in which case update your Withdrawal payload to set useTrustedDestinationAml: true and omit redundant Beneficiary/Destination AML data. This affects Withdrawal API and Wealth Management integrations.Example:Standard custody withdrawal to a Trusted Destination (originator MY_ORGANIZATION):sourceType = SUBACCOUNT):Added
Added Endpoint to Create Trusted Destinations
Added the ability to create trusted destinations via the API, simplifying the process for programmatic use cases. Each request requires quorum approval.Category: Trusted DestinationsEndpoint Added:POST /trusted_destinations: Creates one or more trusted destination addresses (up to 10 per request). Each destination applies to a specific asset address, or to any asset on a network whenisNetworkLevelistrue(e.g., ETH and USDC could both be withdrawn to an ETH address); whenfalse, only the specified asset can be withdrawn to that address. For Wealth Management integrations, the destination can be tied to anownerrepresenting a Wealth ManagementCUSTOMER.
Added
Added Placeholder Template Entry
Added a placeholder endpoint; this changelog record was left as an incomplete template without finalized details.Category: UncategorizedImpact: No functional details were provided in the original record.Added
Added Client Account Onboarding Endpoints and Updated KYC Requirements
Added a new suite of endpoints to create “client accounts” (e.g., Joint, Roth, Custodial) that reference existing onboarding KYC profiles, and updated the KYC application to reduce required information.Category: OnboardingEndpoints Added:POST /onboarding/accounts: Creates a new client account (e.g.,IRA,ROTH,JOINT,CUSTODIAL,INDIVIDUAL_TAXABLE,INSTITUTIONAL_TAXABLE), referencing one or more existing program customers, signers, beneficiaries, and fee configurations.GET /onboarding/accounts/{subaccountId}: Retrieves a client account application.PUT /onboarding/accounts/{subaccountId}: Updates a client account application.POST /onboarding/accounts/{subaccountId}/submit: Submits a client account application for review.
POST /onboarding/customers: For individuals,physicalStateUS/physicalStateOtherare now conditionally required based onphysicalCountry, a newidTypefield (GOVERNMENT_ISSUED_ID_CARDorPASSPORT) determines required identity document uploads, andinitialFundingMethod,sourceOfWealth, andinitialFundingWalletGrouphave been removed. For institutions,physicalStateUS/physicalStateOtherare similarly conditional, newhasDbaName/dbaNamesandconstitutionDocument/proofOfAddressfields were added, andlegalStructure,customerType,countryOfIncorporation,legalRegistAddrDifPrincPlace(and its related address fields),initialFundingWalletGroup, andsourceOfWealthhave been removed.
Added
Added Detailed Level Configuration to Collateral Packages Response
Added new properties to the collateral packages response to provide more detailed information about collateral package levels and their configurations.Category: Collateral ManagementEndpoint Changed:GET /collateral_management/packages: Response now includesmarginReturn,marginCall,acceleratedMarginCall, andcriticalobjects, each containing properties such asltv,action,returnToLtv,warningLtv, anddefaultNotice.
Improved
Improved transactionId Parameter for Subaccount Tax Transactions
Improved: Clarified thetransactionId path parameter description for updating tax transactions.Category: TaxEndpoint Changed:PATCH /tax/transaction/{transactionId}: Now requires the use of the ledgertransactionIdrather than the previous tax transactionid(the Taxbit unique identifier).
id; they must be updated to use the ledger transactionId instead.Deprecated
Deprecated participantId Parameter on Atlas Settlement Rejection
Deprecated: TheparticipantId query parameter is no longer required, and has been removed, from the settlement rejection endpoint.Category: Atlas Settlement NetworkEndpoint Changed:POST /atlas/settlements/{settlementId}/reject: TheparticipantIdquery parameter has been removed.
Added
Added InvalidPrice Reject Reason to Trading Orders
AddedInvalidPrice as a new possible enum value for the rejectReason property.Category: Trading OrdersEndpoint Changed:POST /trading/order:rejectReasonnow includesInvalidPrice, providing a more specific reason for order rejection when the provided price is invalid.
InvalidPrice reason, giving clearer feedback for invalid-price rejections.Improved
Improved Subaccount Transaction Balances Structure
Improved: Theamounts field in subaccount transaction responses now includes a balances array listing supported balance types for each asset and transaction, replacing the previous hold, pending, and posted properties.Category: SubaccountsEndpoints Changed:GET /subaccounts/transactions:amounts.balancesarray replaceshold/pending/postedproperties.GET /subaccounts/transactions/{transactionsIds}:amounts.balancesarray replaceshold/pending/postedproperties.
Improved
Improved Tax Forms Endpoint with Customer-Based Lookup
Improved: Updated parameters for retrieving tax forms to use a customer identifier instead of an affiliate identifier.Category: TaxEndpoint Changed:GET /tax/clients/{customerId}/forms: Path changed from/tax/clients/{affiliateId}/forms; theaffiliateIdpath parameter was removed and replaced withcustomerId.
customerId instead of affiliateId when retrieving tax forms.Example:Deprecated
Deprecated Destination and Beneficiary AML Fields for Transfers
Deprecated: TheDestination and Beneficiary fields within the transfer AML questionnaire, since Anchorage now pulls this data directly from the associated Trusted Destination.Category: TransfersEndpoint Changed:POST /transfers: WithintransferAmlQuestionnaire, the followingDestinationfields are deprecated:destinationType,institutionName,institutionCountry,selfhostedDescription. The followingBeneficiaryfields are deprecated:recipientType,recipientFirstName,recipientLastName,recipientFullName,recipientCountry,recipientStreetAddress,recipientCity,recipientStateProvince,recipientPostalCode.
purpose and originator information need be sent in transferAmlQuestionnaire; Destination and Beneficiary information will now come directly from the AML answers associated with the respective trusted destination.Example:Added
Added Asset-Specific Parameters for Transfers
Added new asset-specific parameter objects to the transfer request body for providing on-chain tags or memos required by certain networks.Category: TransfersEndpoint Changed:POST /transfers: Request body now acceptsassetParametersXRP(destinationTaginteger, for XRP transfers),assetParametersXLM(memostring, for XLM transfers),assetParametersATOM(memostring, for ATOM transfers — now deprecated in favor ofassetParametersCosmos),assetParametersCosmos(memostring, for Cosmos blockchain transfers), andassetParametersExtra(valuestring, for other asset transfers).
Improved
Improved Tax Transactions with Detailed Asset Breakdown
Improved: AddedreceivedAsset, sentAsset, and feeAsset array properties to tax transaction responses for more detailed asset information.Category: TaxEndpoint Changed:GET /tax/transactions/{subaccountId}: Response now includesreceivedAsset(objects withassetType,costBasis,quantityfor deposits/trades),sentAsset(similar, for withdrawals/sales), andfeeAsset(transaction fee detail) arrays. The existingreceived,sent, andfeefields remain unchanged.
Improved
Improved Tax Endpoint Date Formatting and Added Cost Basis Date
Improved: Standardized date-time formatting for tax transaction and cost basis fields, and added a new cost basis date field.Category: TaxEndpoints Changed:GET /tax/transactions/{subaccountId}:transactionTimenow uses a consistent ISO-8601 date-time format.GET /tax/gains/costbasis/{subaccountId}: Added a newcostBasisDatefield (ISO-8601 format);saleDatenow uses a consistent ISO-8601 date-time format.
Improved
Improved Subaccount Withdrawals with Intermediary Bank Support
Improved: Subaccount withdrawal endpoints now support additional bank information fields, including an intermediary financial institution.Category: SubaccountsEndpoints Changed:POST /subaccounts/{subaccountId}/fiat/withdrawals: Request body addsfinancialInstitutionandintermediateFinancialInstitutionobjects (each with nestedaddress,name,id, andcode— enumABA,BIC,DDA);bankAccountNrandbankRoutingNrmoved insidebeneficiary; addedaccountNumberwithinbeneficiaryandcountrywithinbeneficiary.address.GET /subaccounts/{subaccountId}/fiat/withdrawals/{transactionId}: ResponsecustomerDetailsobject now reflects the updated request body fields.
Added
Added Gas Station Support for Atlas Settlements
Added the ability to use the Anchorage Digital Gas Station to cover network fees for Atlas settlements (ETH only).Category: Atlas Settlement NetworkEndpoints Changed:POST /atlas/settlements/{settlementId}/accept: Request body now accepts auseGasStationboolean to have Gas Station cover fees for the acceptor.POST /atlas/settlements: Request body now accepts auseGasStationboolean to have Gas Station cover fees for the proposer.GET /atlas/settlements: Responsedata.proposerSidenow includesgasStationEnabled(boolean, nullable if the caller lacks access to this information).GET /atlas/settlements/{settlementId}: Responsesettlement.proposerSidenow includesgasStationEnabled(boolean, nullable if the caller lacks access to this information).
Improved
Improved Subaccount Transactions with Batch Creation
Improved: The subaccount transaction endpoint now accepts an array of transactions in a single request, enabling atomic creation of multiple subaccount transactions.Category: SubaccountsEndpoint Changed:POST /subaccounts/transactions: Request body now accepts atransactionsarray ofCreateSubaccountTransactionobjects (each withsourceSubaccountId,destinationSubaccountId,assetType,amount, optionaltransactionMemo, andidempotentId), replacing the previous top-level fields of the same names. The200 OKresponse now returns atransactionIdsarray of{transactionId, idempotentId}objects instead of a singletransactionId.
transactions array rather than top-level transaction fields, and to read transactionIds from the response instead of a single transactionId. This enables atomic creation of multiple subaccount transactions in one call, reducing the number of API calls required.Example:Request:Added
Added Tax Form Endpoints for Accounts and Subaccounts
Added new endpoints to retrieve generated tax forms for affiliates and subaccounts.Category: TaxEndpoints Added:GET /tax/clients/{affiliateId}/forms: Retrieves an affiliate’s generated tax forms.GET /tax/subaccounts/{subaccountId}/forms: Retrieves a subaccount’s generated tax forms.
Improved
Improved Tax Transaction Cost Basis Updates with Structured Lots
Improved: The tax transaction update endpoint now accepts a structured JSON payload supporting multiple tax lots.Category: TaxEndpoint Changed:PATCH /tax/transaction/{transactionId}: Request body content type changed toapplication/json; added optionaldataproperty containing nestedassetType(string) andlots(array of objects withacquisitionDatetime,quantity, andcost).
Added
Added Manual Billing Charges API for Wealth Management
Added new endpoints to create and cancel manual billing charges.Category: SubaccountsEndpoints Added:POST /subaccounts/billing/charges: Creates manual billing charges (request body includesidempotentId,interval,feeType, andcharges).DELETE /subaccounts/billing/charges/{chargeId}: Cancels a manual billing charge by itschargeId.
Improved
Improved Deposit Attributions with Date Filtering and New Fields
Improved: Added new query parameters to filter deposit attributions by date, and new fields to the response with blockchain and asset details.Category: Deposit AttributionEndpoint Changed:GET /deposit-attributions/attributions: AddedattributedAtStartDateTimeandattributedAtEndDateTimequery parameters to filter by attribution date; response now includesblockchainTxIdandassetTypefields.