BitGo provides a simple and robust RESTful API and client SDK to integrate digital currency wallets with your application. In Platform V2, we have extended our API and SDK to allow the management of multiple digital currencies and wallets through a single, unified interface.
This is our latest documentation for Platform V2, is generated from OpenAPI 3.0 schema. OpenAPI technology provides improved validation of client requests and more consistency between the API documentation and server-side implementation of API endpoints. The original V2 API docs and V1 docs are still available for your reference.
Legacy users may also refer to the V1 Bitcoin API, which is still available today. There is no dependency for developers to integrate with V1 or read the legacy documentation in order to take advantage of Platform V2.
With a custom endpoint, you gain access to separate resources from the public, www.bitgo.com API. This has the following advantages:
The public API endpoint is more susceptible to spam and attacks by malevolent individuals. With a custom endpoint and a different pool of resources, you will be less likely to be impacted by such attacks.
Your API calls are not processed on the same infrastructure as the public endpoint and do not go through Cloudflare, thus potentially increasing privacy for your requests.
BitGo reserves the right to rate limit requests to our public endpoint. On the enterprise level custom endpoint, users are able to burst requests at a rate of 300 requests per minute or more.
Paying customers on the public endpoint receive an SLA target of 99.95% (more info at https://www.bitgo.com/sla). Custom endpoints receive an SLA target of 99.99%.
In a custom endpoint, your requests are not in the same queue as the public majority, resulting in improved performance.
An enterprise web service like www.bitgo.com is designed to handle a high volume of normal traffic. However malicious actors can hijack thousands or millions of computers in a botnet, and use them to overwhelm a web server with junk traffic. So-called Distributed Denial of Service (DDoS) attacks can block your legitimate traffic from reaching BitGo’s servers.
Since DDoS attacks are targeted at a specific URL or
IP address, one way to prevent your service from
being interrupted is to route your traffic to a different
address. BitGo implements this solution through our
Enterprise customers can opt to use a customized address to route their traffic around a DDoS attack on the main BitGo address. DDoS traffic can’t affect the private address because it is whitelisted by IP address to allow traffic only from customers who request the Custom Endpoint service.
Note that your Custom Endpoint is not a separate instance of the BitGo service. It is simply a different address for accessing your BitGo wallets and reports. You can send transactions, add wallets, and work with your account normally. This will give you three BitGo addresses, depending on your systems.
The cost of the Custom Endpoint is $500/mo per IP address needed from your site. Speak with your BitGo sales representative to set up a Custom Endpoint.
Get started on the same great wallet used by over 40 Bitcoin Exchanges around the world & Integrate multiple digital currencies into your application with a single unified API.