In addition to Developer Portal changelog, you can view granular technical updates from the following:
The Developer Portal now includes a use-case guide called Custody Starter Architecture that walks you through the most common custody integration, designed for clients operating within a single enterprise. This new section is a complete end-to-end guide that you can use to set up the most popular custody configuration.
Custody starter architecture utilizes three wallets for each coin, each with varying degrees of security and balance sizes. This pattern helps your enterprise maximize security while maintaining operational flexibility.
The new guide walks you through creating these three wallets with distinct roles:
Get started with:
BitGo fixed a bug regarding v3 access tokens. These tokens were causing the JavaScript SDK to fall back to v1 authentication, which doesn't include Hash-Based Message Authentication Code (HMAC) .
Now, tokens created with v3 authentication are prefixed with v2x, ensuring they use v2 or v3 authentication protocols with HMAC.
If you're currently using v3 access tokens, BitGo recommends rotating to v2 or v3 access tokens with v2 or v3 authentication. This enables you to have the added security benefits of HMAC.
BitGo extends staking support to Go Accounts. You can now stake assets held in your Go Account and accrue rewards. When you unstake, the assets and rewards become available in your Go Account.
With Go Account staking, BitGo simplifies the required transactions on your behalf, enabling a more streamlined integration experience compared to staking from custody or self-custody wallets.
To learn more, view the API reference and the integration guides:
For clarity, BitGo renames the advanced withdraw flow to manual. This update only impacts the documentation on the Developer Portal - there's no integration impact. The new names impact the following pages:
BitGo now requires using the Partially Signed Bitcoin (PSBT) transaction format for withdrawals of UTXO assets from cold wallets in production. This requirement applies to custody wallets and self-custody cold wallets. This change already took effect in testnet on September 2, 2025.
You must update to a newer version of the OVC. You must also update to a newer version of either BitGo Express or the SDK (depending on your integration).
Ensure you're using the follow versions or higher:
Ensure that when you initiate transactions, the value for the txFormat parameter is psbt or psbt-lite (if you don't pass this parameter, the value defaults to psbt-lite). If txFormat is legacy, BitGo returns an error.
BitGo expands functionality for Crypto-as-a-Service (CaaS) by offering a Know Your Business (KYB) API integration. You can onboard your clients' businesses to your platform, completing regulatory compliance screening programmatically. This update also delivers new webhook functionality to for KYB status monitoring.
View the integration guide at Know Your Business (KYB).
BitGo now requires using the Partially Signed Bitcoin (PSBT) transaction format for withdrawals of UTXO assets from cold wallets in testnet. This requirement applies to custody wallets and self-custody cold wallets.
Note: Beginning September 30, 2025 BitGo will require PSBT in production. Avoid service disruptions by updating your integration before this date.
You must update to a newer version of the OVC. You must also update to a newer version of either BitGo Express or the SDK (depending on your integration).
Ensure you're using the follow versions or higher:
Ensure that when you initiate transactions, the value for the txFormat parameter is psbt or psbt-lite (if you don't pass this parameter, the value defaults to psbt-lite). If txFormat is legacy, BitGo returns an error.
