---
title: "Enable bridging for a wallet"
method: POST
path: "/api/v2/{coin}/wallet/{walletId}/enableBridging"
tags: ["Wallet"]
---

# Enable bridging for a wallet

`POST /api/v2/{coin}/wallet/{walletId}/enableBridging`

Checks the wallet's native balance and requests gas-tank funding if needed.
Returns 400 if the coin does not support the enableBridging feature.
Returns 500 if a downstream service (indexer or gas-tank-service) fails.

## Path parameters

- `coin` string, required — A cryptocurrency symbol or token ticker symbol
- `walletId` string, required

## Request body

- object — No request body parameters required

## Response `200`

OK

- EnableBridgingApiResponse
  - `status` 'funded' | 'funding_initiated' | 'funding_pending' | 'already_funded_insufficient', required — Current funding status
  - `currentBalance` string, required — Current native balance of the wallet's base address in base units
  - `minimumRequired` string, required — Minimum native balance required for bridging in base units
  - `fundingJobId` string — Gas-tank-service funding job ID — present when status is funding_initiated or funding_pending
  - `estimatedConfirmationSeconds` number — Estimated seconds for the funding transaction to confirm
  - `message` string — Human-readable message, typically retry guidance or error explanation

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `500` — Internal Server Error

---

[API](https://skmtc.net/bitgo/apis/bitgo-api.md) · [All operations](https://skmtc.net/bitgo/apis/bitgo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bitgo/bitgo-api/revisions/e445c15e5bee/schema)