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

Blockchain.com Trading API

Authenticated order management and trade history.

Blockchain.com Trading API is one of 12 APIs that Blockchain.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Trading. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 5 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://api.blockchain.info, https://blockchain.info.

8 operations 5 paths 5 schemas 2 DELETE5 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://blockchain.info
Resource Areas
1

Paths & Operations 8

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

Trading 8

Authenticated order management and trade history.

GET
/fees
Blockchain.com Get Maker/taker Fees
getFees → 200
GET
/orders
Blockchain.com List Orders
listOrders 5 params → 200
POST
/orders
Blockchain.com Create a New Order
createOrder body → 200
DELETE
/orders
Blockchain.com Cancel All Open Orders
cancelAllOrders 1 param → 200
GET
/orders/{orderId}
Blockchain.com Get a Single Order
getOrder 1 param → 200
DELETE
/orders/{orderId}
Blockchain.com Cancel a Single Order
cancelOrder 1 param → 200
GET
/trades
Blockchain.com List Trades
listTrades 4 params → 200
GET
/fills
Blockchain.com List Fills
listFills 3 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Order (16 properties), CreateOrderRequest (10 properties), Fill (9 properties), Trade (8 properties). Each schema is shown below with its type and property counts.

Fill
object
A single execution leg, including fees.
9 properties
CreateOrderRequest
object
Payload for submitting a new order.
10 properties 5 required
Fees
object
Maker/taker fee schedule.
3 properties
Order
object
An order submitted to the matching engine.
16 properties
Trade
object
A filled order or partial fill.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

blockchain-trading-api-openapi.yml Raw ↑

Other APIs Blockchain.com publishes across the network.

Blockchain.com WebSocket APIs
Blockchain.com Pay Partner API
Blockchain.com Addresses API
Blockchain.com Blocks API
Blockchain.com Charts API
Blockchain.com Market Data API
Blockchain.com Network API
Blockchain.com Payments API
Blockchain.com Pools API
Blockchain.com Stats API
Blockchain.com Transactions API
Where this information came from

This is an independent, third-party profile of Blockchain.com Trading 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.