Added
Added Stablecoin Reserves Endpoints
Added two new endpoints to the Stablecoins API for retrieving reserve information.Category: StablecoinsEndpoints Added:GET /stablecoins/reserves: Retrieves the history of stablecoin reserves.GET /stablecoins/reserves/entitled-stablecoins: Gets a list of stablecoins for which the organization is entitled to view reserves.
Improved
Improved Response Structure for the List Tags Endpoint Beta
Improved The response body for theGET /tags endpoint now nests the list of tags within a data object for consistency with other API endpoints.Category: TaggingEndpoint Changed:GET /tags: Returns the list of tags nested under adataobject instead of at the top level.
response.data.tags instead of the top-level response.tags.Example:Previous Response Structure:Improved
Improved Field Naming for Creating Wallets on Compatible Networks
Improved ThecreateOnAllCompatibleNetworks field for creating wallets has been renamed to activateAllCompatibleNetworks.Category: WalletsEndpoint Changed:POST /vaults/{vaultId}/wallets: ThecreateOnAllCompatibleNetworksboolean property was removed and replaced byactivateAllCompatibleNetworks.
createOnAllCompatibleNetworks must switch to activateAllCompatibleNetworks to avoid request failures. The field’s behavior is unchanged: when set to true, it activates the new wallet on every network that is key-compatible with the primary networkId and enabled for your organization.Improved
Improved Wallet Creation and Activation Across Compatible Networks
Improved wallet creation and activation to support all compatible networks with a single flag.Category: WalletsEndpoints Changed:POST /vaults/{vaultId}/wallets: Accepts a new optional boolean parameter,createOnAllCompatibleNetworks.POST /wallets/{walletId}/activate: Accepts a new optional boolean parameter,activateAllCompatibleNetworks.
...AllCompatibleNetworks parameters are mutually exclusive with the existing compatibleNetworkIds parameter, so you must provide exactly one of them.Added
Added Endpoints for Tag Management
Added a new Tags API to create, list, and manage tags for entities.Category: TagsEndpoints Added:GET /tags: Lists tags.POST /tags: Creates a tag.POST /tags/apply: Applies tags to an entity.DELETE /tags/apply/{entityId}/{tagName}: Removes a tag from an entity.GET /tags/search: Searches for entities by tag.
Improved
Improved Asset Type Details with Compatible Network IDs
Improved TheGET /asset-types endpoint response now includes a list of compatible network IDs.Category: Asset TypesEndpoint Changed:GET /asset-types: TheAssetTypeDetailsobject now containscompatibleNetworkIds, an array of network IDs that share wallet key derivation with the asset’s primary network.
Added
Added Tax Lot Selection for Async Orders
Added the ability to specify a tax lot ID for async sell orders for tax reporting.Category: TradingEndpoints Changed:POST /trading/async-order: Accepts a new optionalspecLotIdfield to specify a tax lot to retire forSELLorders with atimeInForceofFOK; therejectReasonfield in the response now includesInvalidSideForSpecLotIDandInvalidTimeInForceForSpecLotID.POST /trading/async-order/cancel: TherejectReasonfield in the response now includesInvalidSideForSpecLotIDandInvalidTimeInForceForSpecLotID.
SELL orders, enhancing tax reporting capabilities.Improved
Improved Collateral Package Endpoint with Value and Price Details
Improved The response for the collateral packages endpoint now includes additional value and pricing details for each package and its underlying assets.Category: Collateral ManagementEndpoint Changed:GET /collateral_management/packages: The response now includes optionalexposureValueandpackageValuefields at the top level of each package, plusprice,quantity, andweightedValuefor each asset in thecollateralAssetsarray.
Added
Added Endpoint to Request Collateral Decrease
Added a new endpoint that lets users request a collateral decrease for a specified collateral package.Category: Collateral ManagementEndpoint Added:POST /collateral_management/packages/{packageId}/collateral-decrease: Initiates a two-way Atlas settlement to return assets from the secured party’s collateral wallets to the pledgor’s return wallets.
settlementId is returned in the response for tracking.Example:Added
Added Endpoint to Activate Wallets on Additional Networks
Added a new endpoint to activate an existing wallet on additional compatible networks.Category: WalletsEndpoint Added:POST /wallets/{walletId}/activate: Activates an existing wallet on additional compatible networks.
Added
Added Fiat Details to Transaction Responses
Added A newfiatDetails object is now included in transaction responses to provide banking details for fiat transactions.Category: TransactionsEndpoints Changed:GET /transactions: The response now includes afiatDetailsobject for fiat-related transactions.GET /transactions/{transactionId}: The response now includes afiatDetailsobject for fiat-related transactions.
Added
Added Endpoint to List All Subaccounts
Added a new endpoint to retrieve all subaccounts associated with an organization.Category: SubaccountsEndpoint Added:GET /subaccounts/customers/accounts: Lists all subaccounts for your organization, with filtering bysubaccountIds,externalIds,endDate, andstatuses, plus pagination viaafterIdandlimit.
Improved
Improved Transfers and Withdrawals with Trusted Destination Support
Improved Transfers and withdrawals can now use a Trusted Destination as the destination, and wallet responses can reflect it as a resource type.Category: Transfers, Transactions, WalletsEndpoints Changed:POST /transactions/withdrawal: AcceptsTRUSTED_DESTINATIONas adestination.typevalue.POST /transfers: AcceptsTRUSTED_DESTINATIONas adestination.typevalue.GET /transfers: Can returnTRUSTED_DESTINATIONas a destination type in the response.GET /transfers/{transferId}: Can returnTRUSTED_DESTINATIONas a destination type in the response.GET /vaults/{vaultId}/wallets: Can returnTRUSTED_DESTINATIONas a wallet resource type.POST /vaults/{vaultId}/wallets: Can returnTRUSTED_DESTINATIONas a wallet resource type.GET /wallets: Can returnTRUSTED_DESTINATIONas a wallet resource type.GET /wallets/{walletId}: Can returnTRUSTED_DESTINATIONas a wallet resource type.
Removed
Removed Wallet Activation Endpoint
Removed The endpoint for activating an existing wallet on additional compatible networks has been removed.Category: WalletsEndpoint Removed:POST /wallets/{walletId}/activate
Added
Added Endpoint to Activate Wallets on Additional Networks
Added a new endpoint to activate an existing wallet on additional compatible networks.Category: WalletsEndpoint Added:POST /wallets/{walletId}/activate: Activates an existing wallet on additional compatible networks that share the same key family, without creating a new wallet.
Added
Added Endpoint for Collateral Decrease Requests
Added a new endpoint that lets users request a collateral decrease.Category: Collateral ManagementEndpoint Added:POST /collateral_management/packages/{packageId}/collateral-decrease: Enables programmatic requests to decrease collateral for a specified package.
Added
Added Compatible Networks Support to Wallet Creation
Added an optionalcompatibleNetworkIds field for activating a new wallet on additional compatible networks at the time of creation.Category: WalletsEndpoint Changed:POST /vaults/{vaultId}/wallets: Accepts a new optionalcompatibleNetworkIdsfield (an array of strings).
networkId, and activation happens synchronously after wallet creation.Example:Improved
Improved Memo Handling for Fiat Trusted Destinations
Improved The behavior of thememo field for fiat transfers and withdrawals to Trusted Destinations has been clarified.Category: Transactions, Transfers, and Trusted DestinationsEndpoints Changed:POST /transactions/withdrawal: Thememofield withinassetParametersFiatTrustedDestinationis now optional; if omitted, the default memo from the saved Trusted Destination is used.POST /transfers: Thememofield withinassetParametersFiatTrustedDestinationis now optional; if omitted, the default memo from the saved Trusted Destination is used.GET /trusted_destinations: The response now specifies that thememofor a fiat destination has a maximum length of 140 characters.
Improved
Improved Stablecoin History Response Field Naming
Improved In the response for the stablecoin history endpoint, theissueRedeemId field has been renamed to id.Category: StablecoinsEndpoint Changed:GET /stablecoins/history: The unique identifier for an issue or redeem operation is now returned asidinstead ofissueRedeemId.
issueRedeemId must switch to the new id field.Example:Before:Improved
Improved Stablecoin History Endpoint Pagination and Status Detail
Improved The stablecoin history response now aligns with the standard paginated format and includes more detailed status information.Category: StablecoinsEndpoint Changed:GET /stablecoins/history: The response now returns adataarray plus apageobject for pagination (replacinghasNextPage), addsdestinationOperationIdandsourceOperationId, adds astatusfield (INITIATED,EXECUTING,COMPLETED,FAILED,UNKNOWN), adds an optionalsubStatusfield, and expandsoperationTypeto includeBRIDGEandSWAP.
conversions array is now nested under data, and pagination uses a page.next URL instead of the previous hasNextPage boolean. Integrations must be updated to parse the new response structure.Example:Improved
Improved Order Type Support with LIMIT_ALL_IN
Improved AddedLIMIT_ALL_IN as a new possible enum value for the orderType field in trading order responses.Category: TradingEndpoints Changed:GET /trading/orders: TheorderTypefield in the response may now includeLIMIT_ALL_IN.GET /trading/orders/{orderId}: TheorderTypefield in the response may now includeLIMIT_ALL_IN.
LIMIT_ALL_IN as an orderType. Make sure your client can handle this new value.Improved
Improved Statements with Correction Timestamps and Filtering
Improved Added filtering and timestamp information for corrected statements, so you can track and query statements updated after their initial generation.Category: StatementsEndpoints Changed:GET /statements: Accepts two new optional query parameters,correctedAfterandcorrectedBefore, to filter for statements corrected at or after or before a given time.GET /statements/{statementId}: The response now includes acorrectedAtfield indicating when a correction was made.
Added
Added Subaccount ID Filter for Deposit Attributions
Added You can now filter deposit attributions by one or moresubaccountIds.Category: Deposit AttributionEndpoint Changed:GET /deposit-attributions/attributions: Accepts a new query parameter,subaccountIds.
GET /v2/deposit-attributions/attributions?subaccountIds=subaccount_id_1,subaccount_id_2Improved
Improved Permission Requirements for Stablecoin History
Improved permission requirements for the stablecoin history endpoint.Category: StablecoinsEndpoint Changed:GET /stablecoins/history: Now uses the more specificRead Stablecoin Conversionspermission as the primary requirement.
Read vault activity permission too, so no immediate changes are required for existing integrations.Added
Added Stablecoin Conversion History Endpoint
Added a new endpoint to retrieve the history of stablecoin issuance and redemption operations.Category: StablecoinsEndpoint Added:GET /stablecoins/history: Returns a historical list of your stablecoin issuance and redemption operations.
Added
Added Binance as a Price Source for Collateral Management
Added support forBINANCE as a price source in Collateral Management.Category: Collateral ManagementEndpoints Changed:GET /collateral_management/price_sources: Now returnsBINANCEas an available source and accepts it as a filter in theexchangequery parameter.POST /collateral_management/packages: ThepriceSourcefield now acceptsBINANCE.PATCH /collateral_management/packages/{packageId}: ThepriceSourcefield now acceptsBINANCE.POST /collateral_management/exposures: ThepriceSourcefield now acceptsBINANCE.
Added
Added Accelerated Margin Call for Collateral Management
Added A newacceleratedMarginCall configuration level for collateral packages, letting you set an additional margin call threshold with its own LTV, cure period, and action.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: Accepts a newacceleratedMarginCallobject in the request body.PATCH /collateral_management/packages/{packageId}: Accepts a newacceleratedMarginCallobject in the request body.GET /collateral_management/packages: The response now includes theacceleratedMarginCallobject.
Removed
Removed TRUSTED_DESTINATION Resource Type from Transfers and Wallets
Removed TheTRUSTED_DESTINATION enum value from the destination.type field for transfer and withdrawal requests, and from the type field in several Wallet and Transfer responses.Category: Transfers, Transactions, and WalletsEndpoints Changed:POST /transactions/withdrawal:destination.typeno longer acceptsTRUSTED_DESTINATION; theassetParametersATOMfield is now deprecated in favor ofassetParametersCosmos.POST /transfers:destination.typeno longer acceptsTRUSTED_DESTINATION; theassetParametersATOMfield is now deprecated in favor ofassetParametersCosmos.GET /transfers: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /transfers/{transferId}: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /vaults/{vaultId}/wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.POST /vaults/{vaultId}/wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /wallets/{walletId}: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.
destination.type as TRUSTED_DESTINATION will now fail. To send funds to a trusted destination, use destination.type: 'ADDRESS' with the specific blockchain address, and update any logic that parses the type field in Wallet and Transfer responses. Users are encouraged to migrate from the deprecated assetParametersATOM to assetParametersCosmos.Improved
Improved Order Filtering Parameter Description
Improved the description for theorderTypes query parameter to enhance clarity.Category: TradingEndpoint Changed:GET /trading/orders: The description for theorderTypesparameter was updated.
Improved
Improved Statement Filtering and Response Structure
Improved the Statements endpoints with updated filtering parameters and a restructured response body.Category: StatementsEndpoints Changed:GET /statements: Removed thestatementIds,statementTypes,accountIds,affiliateIds,vaultGroupIds, andsubaccountIdsfilter parameters, and addedids,typeIds, andcustomerIds. The response no longer includesaccountId,affiliateId,subaccountId,vaultGroupId, or the requiredtypefield, and now includescustomerIdand the new requiredtypeIdfield (typeis now optional).GET /statements/{statementId}: The response no longer includesaccountId,affiliateId,subaccountId,vaultGroupId, or the requiredtypefield, and now includescustomerIdand the new requiredtypeIdfield (typeis now optional).
/statements endpoints must be updated to use the new query parameters and handle the modified response structure.Improved
Improved Order Type Support with MANUAL
Improved Added support for a newMANUAL order type.Category: TradingEndpoints Changed:GET /trading/orders: TheorderTypefield in the response can now includeMANUAL.GET /trading/orders/{orderId}: TheorderTypefield in the response can now includeMANUAL.
Improved
Improved Fiat Trusted Destination Response Structure
Improved The structure of thefiat object in the trusted destinations response has been refactored for clarity, with beneficiary and financial institution details now grouped into nested beneficiary and beneficiaryBank objects, plus new intermediaryBank and usage fields.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations: Thefiatobject’s flat beneficiary and institution properties are now nested underbeneficiaryandbeneficiaryBank, and the object gainsintermediaryBankandusagefields.
fiat object must be updated to handle the new nested structure. The new usage field indicates whether the recipient account is owned by your organization or a third party.Example:Before:Added
Added Fiat Support for Trusted Destinations
Added support for fiat (bank account) trusted destinations.Category: Trusted DestinationsEndpoint Changed:GET /trusted_destinations: The response now includes details for fiat-based trusted destinations.
type of fiat and contains a new fiat object with detailed bank account information.Example:Improved
Improved Order Allocation Details with Filled Quantity
Improved Theallocation object in trading order responses now includes the cumQty field, which specifies the filled quantity for each subaccount allocation.Category: TradingEndpoints Changed:POST /trading/order: Theallocationobject in the response now includes the requiredcumQtyfield.GET /trading/orders: Theallocationobject in the response now includes the requiredcumQtyfield.GET /trading/orders/{orderId}: Theallocationobject in the response now includes the requiredcumQtyfield.POST /trading/async-order: Theallocationobject in the response now includes the requiredcumQtyfield.POST /trading/async-order/cancel: Theallocationobject in the response now includes the requiredcumQtyfield.
Improved
Improved Collateral Management Price Sources Endpoint
Improved Added a new501 Not Implemented response and clarified the exchange query parameter description.Category: Collateral ManagementEndpoint Changed:GET /collateral_management/price_sources: Now returns a501 Not Implementederror if the price sources feature is disabled; theexchangeparameter description was simplified.
501 Not Implemented error if the price sources feature is disabled.Improved
Improved Clarity for Tax Reporting Deposit Transaction Endpoints
Improved descriptions for the Tax Reporting endpoints to clarify that cost basis management applies specifically to deposit transactions.Category: Tax ReportingEndpoints Changed:PATCH /tax/accounts/{accountId}/transactions/{transactionId}: The endpoint andhasCostBasisparameter descriptions were improved for accuracy.GET /tax/accounts/{accountId}/transactions: The endpoint andhasCostBasisparameter descriptions were improved for accuracy.
Improved
Improved Async Order Responses with Counter Currency Details
Improved AddedcounterCurrency, counterQty, and counterQtyAllIn fields to the responses for placing and canceling async orders.Category: TradingEndpoints Changed:POST /trading/async-order: The response now includescounterCurrency,counterQty, andcounterQtyAllIn.POST /trading/async-order/cancel: The response now includescounterCurrency,counterQty, andcounterQtyAllIn.
Added
Added Collateral Management Price Sources Endpoint
Added a new endpoint to get available price sources and their supported assets.Category: Collateral ManagementEndpoint Added:GET /collateral_management/price_sources: Returns supported price sources and the specific assets available for each source.
Improved
Improved Price Strategy Options for Collateral Management
Improved ThepriceStrategy options for creating and managing collateral packages and exposures now include MID and LAST; VWAP has been removed.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceStrategyfield now acceptsMIDandLAST;VWAPis no longer supported.PATCH /collateral_management/packages/{packageId}: ThepriceStrategyfield now acceptsMIDandLAST;VWAPis no longer supported.POST /collateral_management/exposures: ThepriceStrategyfield now acceptsMIDandLAST;VWAPis no longer supported.
priceStrategy field must switch from VWAP to MID or LAST.Added
Added Fiat Parameters for Trusted Destination Transfers and Withdrawals
Added A newassetParametersFiatTrustedDestination object to the request body for fiat transfers and withdrawals to Trusted Destinations.Category: Transactions, TransfersEndpoints Changed:POST /transactions/withdrawal: Accepts a new optionalassetParametersFiatTrustedDestinationobject withmemoandpurposefields.POST /transfers: Accepts a new optionalassetParametersFiatTrustedDestinationobject withmemoandpurposefields.
Improved
Improved Offchain Vesting Schedule Response with Asset Type
Improved the response for listing offchain vesting schedules to include the asset type.Category: VestingEndpoint Changed:GET /offchainvesting/schedules: Each schedule object in thedataarray now includes theassetTypefield, specifying the asset abbreviation (for example, BTC or ETH).
Improved
Improved Transfers and Withdrawals with Trusted Destinations
Improved You can now use pre-configured Trusted Destinations when creating transfers and withdrawals, sending funds to aTRUSTED_DESTINATION ID instead of a full address.Category: Transfers & WithdrawalsEndpoints Changed:POST /transfers: Thedestination.typefield now acceptsTRUSTED_DESTINATION.POST /transactions/withdrawal: Thedestination.typefield now acceptsTRUSTED_DESTINATION.GET /transfers: The response can now reflectTRUSTED_DESTINATIONas a destination type.GET /transfers/{transferId}: The response can now reflectTRUSTED_DESTINATIONas a destination type.
TRUSTED_DESTINATION, you no longer need to include asset-specific parameters like assetParametersXRP or assetParametersXLM — the destination tag or memo is inherited automatically from the trusted destination’s configuration.Example:Improved
Improved Market Data Endpoint with Amount-Based Depth
Improved The market data endpoint now supports returning market depth by notional value, such as USD, in addition to asset size.Category: TradingEndpoint Changed:GET /trading/marketdata: A newamountfield has been added to thebidsandoffersobjects, returned when using theamountBucketsquery parameter; the existingsizefield is returned when usingsizeBuckets.
Added
Added Endpoint to Propose Trusted Counterparties
Added A new endpoint to propose a new trusted counterparty.Category: Atlas Settlement NetworkEndpoint Added:POST /atlas/directory/counterparties: Proposes a new trusted counterparty.
Improved
Improved Market Data Parameter Descriptions
Improved descriptions for thesizeBuckets and amountBuckets query parameters to clarify their usage and impact on the response.Category: TradingEndpoint Changed:GET /trading/marketdata:sizeBucketsis clarified as a comma-separated list;amountBucketsis clarified as a comma-separated list of USD values, with a note that using it affects howsizeis represented in the response.
Improved
Improved Cost Basis Reporting with Tax Lots
Improved the Tax Reporting endpoints to support lot-level cost basis management for more granular and accurate tax data.Category: Tax ReportingEndpoints Changed:PATCH /tax/accounts/{accountId}/transactions/{transactionId}: The request body now requires alotsarray (each withlotId,quantity, andcostBasis) in place of the previousdata,acquisitionDatetime, andassetTypefields.GET /tax/accounts/{accountId}/transactions: The response now includes a required top-levelassetTypefield per transaction, and anacquisitionDatetimefield on each lot in thereceivedAssetsarray.
Added
Added Market Data Endpoint
Added a new endpoint to retrieve a snapshot of market data.Category: TradingEndpoint Added:GET /trading/marketdata: Returns a snapshot of current market data.
Improved
Improved Transaction Types and Settlement Parameter Documentation
Improved Added theFIAT_INTEREST transaction type and clarified the applyPostLock parameter description.Category: Transactions, Atlas Settlement NetworkEndpoints Changed:GET /transactions: ThetransactionTypefield in the response can now includeFIAT_INTEREST, representing fiat interest payments.GET /transactions/{transactionId}: ThetransactionTypefield in the response can now includeFIAT_INTEREST, representing fiat interest payments.POST /atlas/settlements: The description for theapplyPostLockparameter now clarifies it applies only to clients using Atlas settlements integrated with Anchorage Vesting.
FIAT_INTEREST transaction type. The applyPostLock documentation change is non-breaking and only clarifies existing behavior.Deprecated
Deprecated totalDistribution Field in Tax Tagging
Deprecated the totalDistribution field for tagging tax transactions.Category: TaxEndpoint Changed:POST /tax/transaction/{transactionId}/tag: ThetotalDistributionfield in the request body is now deprecated and ignored if provided.
totalDistribution is disregarded — total distribution status is now calculated automatically from account balances. Remove this field from your requests, since it no longer has any effect.Added
Added Post-Settlement Locking for Atlas Settlements
Added a newapplyPostLock parameter to automatically create post-settlement holds on funds received through the Atlas Settlement Network.Category: Atlas Settlement NetworkEndpoint Changed:POST /atlas/settlements: Accepts a new optional booleanapplyPostLockparameter; whentrue, indefinite holds are placed on the acceptor’s destination wallets after a successful settlement.
Added
Added Vesting Schedules Endpoint and Tax Transaction Cost Basis Filter
Added a new endpoint for listing offchain vesting schedules and a new filter for tax transactions.Category: Vesting, Tax ReportingEndpoints Changed:GET /offchainvesting/schedules: New endpoint that lists all offchain vesting schedules for your organization.GET /tax/accounts/{accountId}/transactions: Accepts a newhasCostBasisquery parameter to filter transactions that do or don’t have a cost basis.
Improved
Improved Transaction Types with Priority Fee Reward
Improved ThetransactionType field in transaction-related endpoints now includes PRIORITY_FEE_REWARD to represent priority fee rewards.Category: TransactionsEndpoints Changed:GET /transactions: ThetransactionTypefield in the response can now includePRIORITY_FEE_REWARD.GET /transactions/{transactionId}: ThetransactionTypefield in the response can now includePRIORITY_FEE_REWARD.
Improved
Improved Clarity for Trusted Destination Asset Type
Improved The description for theassetType field has been updated to provide better clarity when creating a trusted destination.Category: Trusted DestinationsEndpoint Changed:POST /trusted_destinations: The description forassetTypein thetrustedDestinationsarray now clarifies what an asset type is and points toGET /asset-typesfor a list of supported types.
Improved
Improved Security with Signature Requirements for Collateral Management
Improved security by requiringApi-Signature and Api-Timestamp headers for write operations on Collateral Management endpoints.Category: Collateral ManagementEndpoints Changed:PATCH /collateral_management/operations/{operationId}: Now requiresApi-SignatureandApi-Timestampheaders.PATCH /collateral_management/packages/{packageId}: Now requiresApi-SignatureandApi-Timestampheaders.POST /collateral_management/exposures: Now requiresApi-SignatureandApi-Timestampheaders.POST /collateral_management/operations: Now requiresApi-SignatureandApi-Timestampheaders.POST /collateral_management/packages: Now requiresApi-SignatureandApi-Timestampheaders.
Improved
Improved Wallet Responses with Unvested and Unstakeable Balances
Improved Wallet-related endpoints now include more detailed balance information for offchain vesting.Category: WalletsEndpoints Changed:GET /vaults/{vaultId}/wallets: Theassetsobject now includesunvestedBalanceandunvestedUnstakeableBalancefields.POST /vaults/{vaultId}/wallets: Theassetsobject now includesunvestedBalanceandunvestedUnstakeableBalancefields.GET /wallets: Theassetsobject now includesunvestedBalanceandunvestedUnstakeableBalancefields.GET /wallets/{walletId}: Theassetsobject now includesunvestedBalanceandunvestedUnstakeableBalancefields.
Improved
Improved Vesting Balance Retrieval for Multiple Allocations
Improved vesting balance retrieval by adding a new endpoint to fetch balances for multiple allocations in a single request.Category: VestingEndpoint Added:POST /vesting/balances: Retrieves vesting balances for multiple allocations in a single request.
Improved
Improved Security with Request Signing for Atlas Settlement Endpoints
Improved security by adding request signing to key Atlas Settlement Network endpoints, which now requireApi-Signature and Api-Timestamp headers.Category: Atlas Settlement NetworkEndpoints Changed:POST /atlas/settlements: Now requiresApi-SignatureandApi-Timestampheaders.POST /atlas/settlements/{settlementId}/accept: Now requiresApi-SignatureandApi-Timestampheaders.POST /atlas/settlements/{settlementId}/authorize: Now requiresApi-SignatureandApi-Timestampheaders.POST /atlas/settlements/{settlementId}/reject: Now requiresApi-SignatureandApi-Timestampheaders.
Improved
Improved Stablecoin Conversion Documentation
Improved the description for thesourceAssetType field in the stablecoin conversion request body for clarity.Category: StablecoinsEndpoint Changed:POST /stablecoins/conversion: ThesourceAssetTypedescription now clarifies that it must beUSDfor an issuance, and the asset being redeemed for a redemption.
Improved
Improved Staking Request Descriptions
Improved The descriptions for theparameters object and the stakingProviderAddress field for Solana staking requests have been updated for clarity.Category: TransactionsEndpoint Changed:POST /transactions/stake: The description for theparametersobject was updated, and withinSOLStakingParameters,stakingProviderAddressnow describes “the validator’s vote account address” instead of “the validator’s staking address”.
Added
Added Endpoint for Consolidating Stakes
Added a new endpoint to create a consolidate stake request.Category: TransactionsEndpoint Added:POST /transactions/consolidate-stake: Initiates a request to consolidate staking positions.
Improved
Improved Backward Compatibility by Re-introducing the VAULT Resource Type
Improved backward compatibility by re-introducing theVAULT enum value for source and destination resources; it’s accepted but deprecated in favor of WALLET.Category: Transfers, Wallets, and TransactionsEndpoints Changed:POST /transactions/withdrawal: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.POST /transfers: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.GET /transfers: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.GET /transfers/{transferId}: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.GET /vaults/{vaultId}/wallets: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.POST /vaults/{vaultId}/wallets: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.GET /wallets: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.GET /wallets/{walletId}: AcceptsVAULTagain as a resource type, though deprecated in favor ofWALLET.
VAULT resource type. We strongly recommend updating existing code to use WALLET instead, since support for VAULT will be removed in a future release.Fixed
Fixed AML Questionnaire Requirement by Organization Type
Fixed ThetrustedDestinationAmlQuestionnaire field is now conditionally required based on the organization type.Category: Trusted DestinationsEndpoint Changed:POST /trusted_destinations: ThetrustedDestinationAmlQuestionnairefield is now required for Anchorage Digital organizations and must be omitted for Porto organizations.
trustedDestinationAmlQuestionnaire is included for a Porto organization or omitted for an Anchorage Digital organization.Added
Added Endpoints for Tax Account Management
Added new endpoints to the Tax API for managing tax accounts and their associated transactions.Category: TaxEndpoints Added:GET /tax/accounts: Lists tax accounts.GET /tax/accounts/{accountId}/transactions: Retrieves transactions for a specific tax account.PATCH /tax/accounts/{accountId}/transactions/{transactionId}: Updates the cost basis of a transaction for tax reporting.
Removed
Removed TRUSTED_DESTINATION as a Resource Type
Removed TheTRUSTED_DESTINATION value as a valid enum for the resource type field.Category: Transfers, Withdrawals, WalletsEndpoints Changed:POST /transactions/withdrawal: Thedestination.typefield no longer acceptsTRUSTED_DESTINATION.POST /transfers: Thedestination.typefield no longer acceptsTRUSTED_DESTINATION.GET /transfers: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /transfers/{transferId}: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /vaults/{vaultId}/wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.POST /vaults/{vaultId}/wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /wallets: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.GET /wallets/{walletId}: Thetypefield in responses no longer returnsTRUSTED_DESTINATION.
destination.type: TRUSTED_DESTINATION will now fail. Specify the underlying ADDRESS or WALLET directly when creating transfers or withdrawals.Improved
Improved Tax Transaction Tagging with IRS Combination Codes
Improved ThedistributionCode field for tagging tax transactions now supports IRS combination codes.Category: TaxEndpoint Changed:POST /tax/transaction/{transactionId}/tag: ThedistributionCodefield now accepts combination codes (for example,1B,4G,7B) as valid enum values.
4G for a death-related direct rollover.Improved
Improved Collateral Management Operations with Liquidation Details
Improved The response for Collateral Management Operations now includes liquidation details and an update timestamp.Category: Collateral ManagementEndpoints Changed:PATCH /collateral_management/operations/{operationId}: TheCMOperationmodel now includesupdatedAt,liquidationCollateralPackageId,liquidationProceedAsset, andliquidationProceedQuantity.GET /collateral_management/operations: TheCMOperationmodel now includesupdatedAt,liquidationCollateralPackageId,liquidationProceedAsset, andliquidationProceedQuantity.
Improved
Improved API Key Info Response with WRITE_TAX Permission
Improved Added the newWRITE_TAX permission type, which now appears in the response for the get API key info endpoint.Category: API KeyEndpoint Changed:GET /apikey: Thepermissionsarray in the response now includesWRITE_TAXfor API keys that have this permission.
Added
Added AML Questionnaire to Trusted Destination Creation
Added an optionaltrustedDestinationAmlQuestionnaire object to the request body for creating trusted destinations, so Anti-Money Laundering information can be submitted upfront.Category: Trusted DestinationsEndpoint Changed:POST /trusted_destinations: Accepts an optionaltrustedDestinationAmlQuestionnaireobject within each item of thetrustedDestinationsarray.
Improved
Improved Deposit Address Security with V2 Signatures
Improved security by introducing a V2 signature scheme for deposit addresses.Category: Addresses, WalletsEndpoints Changed:GET /vaults/{vaultId}/addresses: Signed address responses can now includesignatureVersionandcertChainfields.POST /wallets/{walletId}/addresses: Signed address responses can now includesignatureVersionandcertChainfields.GET /vaults/{vaultId}/wallets: Signed address responses can now includesignatureVersionandcertChainfields.POST /vaults/{vaultId}/wallets: Signed address responses can now includesignatureVersionandcertChainfields.GET /wallets: Signed address responses can now includesignatureVersionandcertChainfields.GET /wallets/{walletId}: Signed address responses can now includesignatureVersionandcertChainfields.
signatureVersion is V2, the certChain field contains an x509 certificate chain for verification against a trusted Anchorage Digital Root CA; if certChain is absent, use the existing V1 signature verification method. See the Address Verification guide for instructions.Added
Added MINT Transaction Type
AddedMINT as a new transaction type to represent assets minted or created on the blockchain.Category: TransactionsEndpoints Changed:GET /transactions: Thetypesquery parameter now acceptsMINTto filter transactions, and thetransactionTypefield in the response can now returnMINT.GET /transactions/{transactionId}: ThetransactionTypefield in the response can now returnMINT.
MINT transactions across both the list and single-transaction endpoints.Improved
Improved Error Handling for Collateral Package Updates
Improved error handling by adding a new422 Unprocessable Entity error response to the update collateral package endpoint.Category: Collateral ManagementEndpoint Changed:PATCH /collateral_management/packages/{packageId}: Now returns422 Unprocessable Entityfor requests that are syntactically correct but semantically invalid.
400), a resource not found (404), and an unprocessable entity (422).Improved
Improved Pricing Options for Collateral Management
Improved Added new options for price strategy and price source to provide more flexibility in Collateral Management configurations.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceStrategyfield now acceptsVWAP, and thepriceSourcefield now acceptsKAMINO.PATCH /collateral_management/packages/{packageId}: ThepriceStrategyfield now acceptsVWAP, and thepriceSourcefield now acceptsKAMINO.POST /collateral_management/exposures: ThepriceStrategyfield now acceptsVWAP, and thepriceSourcefield now acceptsKAMINO.
VWAP (Volume-Weighted Average Price) as a pricing strategy and KAMINO as a price source when creating or updating collateral packages and exposures.Added
Added BURN Transaction Type
Added a newBURN transaction type to represent assets that are burned or destroyed on the blockchain.Category: TransactionsEndpoints Changed:GET /transactions: Thetypesquery parameter now acceptsBURNto filter transactions, and thetransactionTypefield in the response can now returnBURN.GET /transactions/{transactionId}: ThetransactionTypefield in the response can now returnBURN.
Removed
Removed priceSourceProvider from Collateral Management Endpoints
Removed thepriceSourceProvider field from the request bodies of several Collateral Management endpoints.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceSourceProviderfield is no longer available incollateralAssetsConfig.PATCH /collateral_management/packages/{packageId}: ThepriceSourceProviderfield is no longer available incollateralAssetsConfig.POST /collateral_management/exposures: ThepriceSourceProviderfield is no longer available inassetTrackingConfig.
priceSourceProvider field will now result in an error. Update your integrations to remove this field to ensure successful requests.Improved
Improved Collateral Management Operations with GAS_FEE Action
Improved theCMOperation model to include a new GAS_FEE action type.Category: Collateral ManagementEndpoints Changed:PATCH /collateral_management/operations/{operationId}: Theactionfield in the response can now includeGAS_FEE.GET /collateral_management/operations: Theactionfield in the response can now includeGAS_FEE.
Improved
Improved Fiat Deposit Instructions with Memo Field
Improved AmemoField has been added to the depositInstruction object returned for fiat wallets.Category: WalletsEndpoints Changed:GET /vaults/{vaultId}/wallets: ThedepositInstructionobject for fiat wallets now includesmemoField.POST /vaults/{vaultId}/wallets: ThedepositInstructionobject for fiat wallets now includesmemoField.GET /wallets: ThedepositInstructionobject for fiat wallets now includesmemoField.GET /wallets/{walletId}: ThedepositInstructionobject for fiat wallets now includesmemoField.
Improved
Improved Wallet Details with Fiat Deposit Instructions
Improved Wallet-related endpoints now include adepositInstruction object with banking details for fiat wallets, distinct from crypto wallet addresses.Category: WalletsEndpoints Changed:GET /vaults/{vaultId}/wallets: The response now conditionally includes thedepositInstructionobject for fiat wallets.POST /vaults/{vaultId}/wallets: The response now conditionally includes thedepositInstructionobject for fiat wallets.GET /wallets: The response now conditionally includes thedepositInstructionobject for fiat wallets.GET /wallets/{walletId}: The response now conditionally includes thedepositInstructionobject for fiat wallets.
depositAddress object remains for crypto wallets. The description for the assets array has also been clarified to state that it may be empty.Example:Improved
Improved Collateral Management Package Updates and API Refinements
Improved the Collateral Management API for more comprehensive control and clarity, including support for partial updates to a package’s entire configuration.Category: Collateral ManagementEndpoints Changed:PATCH /collateral_management/packages/{packageId}: You can now update nearly all configuration details of a package, includingclientReferenceId,collateralAssetsConfig,ltvRoundingPrecision,priceStrategy, and settings forcritical,marginCall,marginReturn, andautoDeleveraginglevels; omitted fields remain unchanged.PATCH /collateral_management/operations/{operationId}: Thetypefield no longer accepts theLIQUIDATIONenum value, and thetypeIddescription was improved for clarity.POST /collateral_management/operations: Thetypefield no longer accepts theLIQUIDATIONenum value, and thetypeIddescription was improved for clarity.GET /collateral_management/exposures: Field descriptions were updated for accuracy and clarity.POST /collateral_management/packages: Field descriptions were updated for accuracy and clarity.GET /collateral_management/packages: Field descriptions were updated for accuracy and clarity.
Added
Added Collateral Management Operation Actions
Added newaction types for creating and updating Collateral Management operations.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/operations: Theactionfield now supportsCLOSE_RETURN,REHYPE_IN, andREHYPE_OUT.PATCH /collateral_management/operations/{operationId}: Theactionfield now supportsCLOSE_RETURN,REHYPE_IN, andREHYPE_OUT.
Added
Added Fields for Tax Transaction Tagging
Added new conditional fields for tagging tax transactions to support more detailed reporting.Category: TaxEndpoint Changed:POST /tax/transaction/{transactionId}/tag: The request body now supportsdistributionCode(required whentagisdistribution),totalDistribution(required whentagisdistribution), andpostponedLateReason(required whentagispostponedorlate-rollover).
distribution, postponed, or late-rollover, you must now provide these additional details for more accurate tax reporting.Example:Improved
Improved Collateral Management API Clarity and Field Support
Improved several Collateral Management endpoints for clarity and functionality, with updated field descriptions and examples throughout.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: Removed thedefaultGroupIdparameter from the request body.GET /collateral_management/packages: RemovedacceleratedMarginCallfrom the response, and addedCURE_PERIOD_EXPIREDandDEFAULTEDto thestateenum.POST /collateral_management/exposures: Descriptions improved for clarity.GET /collateral_management/exposures: Descriptions improved for clarity.POST /collateral_management/operations: Removed several unsupported enum values from theactionfield to reflect currently available actions.GET /collateral_management/operations: Descriptions improved for clarity.PATCH /collateral_management/operations/{operationId}: Removed several unsupported enum values from theactionfield to reflect currently available actions.
clientReferenceId, pledgorId, curePeriod, ltv, and topUpType, giving clearer guidance when configuring collateral packages, exposures, and operations.Improved
Improved Price Strategy Options with BID and ASK
Improved AddedBID and ASK as valid options for the priceStrategy field when creating collateral packages and exposures.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceStrategyfield now acceptsBIDandASK.POST /collateral_management/exposures: ThepriceStrategyfield now acceptsBIDandASK.
Improved
Improved Filtering for List Orders Endpoint
Improved order filtering capabilities by adding a neworderTypes parameter.Category: TradingEndpoint Changed:GET /trading/orders: Accepts a new optionalorderTypesquery parameter, an array of strings to filter by order type (LIMIT,MARKET,STOP_LOSS,STOP_LIMIT,TAKE_PROFIT_LIMIT,TWAP,VWAP,PEGGED,POV,OTHER).
GET /v2/trading/orders?orderTypes=LIMIT,STOP_LIMITImproved
Improved Customer Onboarding with Single-Call Submission
Improved the customer onboarding workflow by adding an optionalsubmit parameter.Category: OnboardingEndpoint Changed:POST /onboarding/customers: Accepts a new optional booleansubmitparameter.
submit is true, the application is created and submitted in a single call, eliminating the need for a separate submission request and reducing the number of required API calls.Improved
Improved Price Source Options with KRAKEN
Improved AddedKRAKEN as a supported price source for collateral management.Category: Collateral ManagementEndpoints Changed:POST /collateral_management/packages: ThepriceSourcefield now acceptsKRAKEN.POST /collateral_management/exposures: ThepriceSourcefield now acceptsKRAKEN.