How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bakkt Transfers API

Transfers allow users to access deposit and withdrawal functionality both within the Bakkt network and across the blockchain.

Bakkt Transfers API is one of 17 APIs that Bakkt publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transfers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.0.0, at version 2.0.

Requests are made against a single base URL, https://api.bakkt.com.

6 operations 6 paths 12 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.0
Base URL
https://api.bakkt.com
Terms of Service
Resource Areas
1

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Transfers 6

Transfers allow users to access deposit and withdrawal functionality both within the Bakkt network and across the blockchain.

GET
/apex-crypto/api/v2/transfers/withdraw/coin/{clientTransactionId}
Retrieve the Withdrawal Status
getWithdraw 1 param → 200404default
GET
/apex-crypto/api/v2/transfers/vaspLookup/{receivingWallet}
Lookup the name of a vasp associated with a wallet address.
lookupVasp 2 params → 200404default
POST
/apex-crypto/api/v2/transfers/deposit/coin/receiveAddress
Retrieve a Wallet Receive Address
postReceiveAddress body → 200400default
POST
/apex-crypto/api/v2/transfers/withdraw/coin
Create a Crypto Withdrawal Request
postWithdraw body → 200400default
POST
/apex-crypto/api/v2/transfers/withdraw/coin/estimate
Retrieve a Fee Estimate to Complete a Withdrawal
postWithdrawFee body → 200default
POST
/apex-crypto/api/v2/transfers/verifyWalletAddress
Verify that a wallet address is valid prior to using it in a transfer request.
verifyWalletAddress body → 200default

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are WithdrawRequest (15 properties), Withdrawal (11 properties), WithdrawalEstimatedFeeResponse (9 properties), WithdrawalEstimatedFeeRequest (4 properties). Each schema is shown below with its type and property counts.

VaspLookupResponse
object
1 property 1 required
WithdrawalStatus
string
WithdrawalEstimatedFeeResponse
object
9 properties 8 required
Withdrawal
object
11 properties 4 required
VerifyWalletAddressResponse
object
3 properties 2 required
DepositReceiveAddressResponse
object
4 properties 2 required
WithdrawalEstimatedFeeRequest
object
4 properties 2 required
DepositReceiveAddressRequest
object
3 properties 2 required
Error
object
2 properties 2 required
WithdrawRequest
object
15 properties 6 required
Network
string
VerifyWalletAddressRequest
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bakkt-transfers-api-openapi.yml Raw ↑

Other APIs Bakkt publishes across the network.

Bakkt Accounts API
Bakkt Authorization API
Bakkt Block Trade & Allocate API
Bakkt Configuration and Status API
Bakkt Currency Onboarding API
Bakkt Documents API
Bakkt Fiat Onboarding API
Bakkt Gift API
Bakkt Instruments API
Bakkt Jurisdictions API
Bakkt Orders API
Bakkt Partner Connectivity API
Where this information came from

This is an independent, third-party profile of Bakkt Transfers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.