BitGo has a test environment and a production environment. Both environments use the same set of APIs to interact with digital assets, but the test environment enables you to transact using freely-obtained testnet coins.

The environments are entirely separate from each other - there's no syncing in either accounts or data across environments. Therefore, you need to create accounts for both the test and production environments, and configure your apps separately for each. BitGo doesn't reset the environments. Once created, all of your data persists within their environment.

For security reasons, all BitGo API requests are made using TLS over HTTPS.

Test Environment

The test environment is: https://app.bitgo-test.com/web/auth/login

The BitGo developer portal and the test environment share login credentials. Creating an account for the developer portal automatically creates an enterprise in the test environment.

Our test environment connects to the testnet networks of the coins we support. You can obtain free testnet coins from faucets. Testnet coins don't hold real monetary value. For example bitcoin (BTC) and ethereum (ETH) both have testnet versions, TBTC and HTETH, respectively. However, production tokens often don't have a testnet equivalent, because tokens typically exist as smart contracts on live blockchains.

While in the test environment, you can use the value 0000000 in place of a one-time password (OTP) when authenticating.

Note: If you're a custodial-wallet customer and want to have withdrawal approved in the test environment, you must contact us to request it.

Production Environment

The production environment is: https://app.bitgo.com/web/auth/login

To use the production environment, specify { env: 'prod' } when using the SDK or -e prod when running the Express API. When operating in the Production environment, provide SSL certificates to secure traffic to and from the Express API instances.

Note All of our code samples use the test environment. When you're ready to create an app in production, update your code with the production URL.