Overview
BitGo Express is a lightweight service that you host in your own data center. It acts as a local proxy to the BitGo REST API, enabling you to run sensitive operations — such as partially signing transactions — client-side. Your private keys never leave your network and are never seen by BitGo.
Because BitGo Express is a standalone HTTP server, it is language agnostic. You can call its endpoints from any language or framework using standard HTTP requests.
Note: The API explorer is not available for Express endpoints. To test these endpoints, you must run an Express server locally. For setup instructions, see Install BitGo Express.
OpenAPI 3.0 Specification
You can download the BitGo OpenAPI 3.0 specification as a JSON or YAML file and run it in tools like Swagger UI or Postman
Make Requests
All Express endpoints are served from the local Express server (default http://localhost:3080). Requests follow the same authentication and JSON conventions as the BitGo REST API:
curl \
-X POST \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ ... }' \
http://localhost:3080/api/v2/{coin}/wallet/{walletId}/sendcoinsRun Express
BitGo recommends running Express via the official Docker container:
docker pull --platform linux/amd64 bitgo/express:latest
docker run --platform linux/amd64 -it -p 3080:3080 bitgo/express:latestFor production deployments, you must enable TLS. See Run Express in Production for details.
Configure
You can configure Express using command-line arguments or environment variables. Common options include:
| Option | Environment Variable | Default | Description |
|---|---|---|---|
--port | BITGO_PORT | 3080 | Port Express listens on. |
--bind | BITGO_BIND | localhost | Interface Express listens on. Use 0.0.0.0 for all interfaces. |
--env | BITGO_ENV | test | BitGo environment (test or prod). |
--keypath | BITGO_KEYPATH | N/A | Path to SSL .key file. Required in production. |
--crtpath | BITGO_CRTPATH | N/A | Path to SSL .crt file. Required in production. |
For a full list of configuration parameters, see Reference Configuration Parameters.