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

Upbit Exchange - Withdrawals API

Withdrawal management endpoints — JWT required

Upbit Exchange - Withdrawals API is one of 8 APIs that Upbit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Exchange - Withdrawals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.

This API exposes 7 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 1.3.2.

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

7 operations 6 paths 1 schemas 1 DELETE4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.3.2
Base URL
https://api.upbit.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Upbit Exchange - Withdrawals API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — JWT HS512 token generated from Access Key and Secret Key. Include queryhash and queryhashalg=SHA512 in the payload when query parameters or JSON body exist.

Paths & Operations 7

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

Exchange - Withdrawals 7

Withdrawal management endpoints — JWT required

GET
/withdraws/chance
Get available withdrawal information
getAvailableWithdrawalInformation 2 params → 200401
POST
/withdraws/coin
Request digital asset withdrawal
withdrawCoin body → 201401
DELETE
/withdraws/coin
Cancel digital asset withdrawal
cancelWithdrawal 1 param → 200401404
POST
/withdraws/krw
Request KRW withdrawal
withdrawKrw body → 201401
GET
/withdraw
Get withdrawal
getWithdrawal 3 params → 200401
GET
/withdraws
List withdrawals
listWithdrawals 9 params → 200401
GET
/withdraws/coin_addresses
List withdrawal addresses
listWithdrawalAddresses → 200401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WithdrawalResponse (10 properties). Each schema is shown below with its type and property counts.

WithdrawalResponse
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upbit-exchange-withdrawals-api-openapi.yml Raw ↑

Other APIs Upbit publishes across the network.

Upbit WebSocket API
Upbit Exchange - Account API
Upbit Exchange - Deposits API
Upbit Exchange - Orders API
Upbit Exchange - Service API
Upbit Exchange - Travel Rule API
Upbit Quotation API
Where this information came from

This is an independent, third-party profile of Upbit Exchange - Withdrawals 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.