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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Bullish

Bullish History API

The history API from Bullish — 5 operation(s) for history.

Documentation Provider Profile APIs.io OpenAPI GitHub

Bullish History API is one of 32 APIs that Bullish publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, and a changelog.

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

Requests are made against 7 base URLs: https://api.exchange.bullish.com/trading-api, https://registered.api.exchange.bullish.com/trading-api, https://prod.access.bullish.com/trading-api, https://api.bugbounty.bullish.com/trading-api, https://api.simnext.bullish-test.com/trading-api, https://registered.api.simnext.bullish-test.com/trading-api, https://simnext.access.bullish.com/trading-api.

5 operations 5 paths 28 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.exchange.bullish.com/trading-api
Authentication
HTTP Bearer
Contact
Bullish Help Center
Resource Areas
1

Authentication & Security 1

Bullish History API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtTokenAuth).

Paths & Operations 5

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

history 5
GET
/v2/history/orders
Get Historical Orders
getOrdersHistoryV2 8 params → 200401403429500
GET
/v1/history/trades
Get Historical Trades
getTradesHistory 9 params → 200401403429500
GET
/v1/history/derivatives-settlement
Get Historical Hourly Derivatives Settlement
getDerivativesSettlementHistory 4 params → 200429500
GET
/v1/history/transfer
Get Historical Account Transfer
getTransferHistory 6 params → 200429500
GET
/v1/history/borrow-interest
Get Historical Hourly Borrow Interest
getBorrowInterestHistory 4 params → 200404429500

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Order (23 properties), Trade (18 properties), DerivativesSettlementResponse (13 properties), SubAccountTransferResponse (10 properties). Each schema is shown below with its type and property counts.

MarketSymbol
string
market symbol. E.g. BTCUSDC
DatedFutureMarketSymbol
string
market symbol. E.g. BTC-USDC-PERP for PERPETUAL and BTC-USDC-20241201 for DATED FUTURE markets.
OrderTypeAsString
string
order type can have the following string values "LMT", "MKT", "STOPLIMIT", "POSTONLY". "MKT" and "STOPLIMIT" are not applicable for Options
AssetID
string
unique asset ID
TradeID
string
OrderSideAsString
string
order side can have the following string values "BUY", "SELL"
Order
object
23 properties 21 required
SubAccountTransferResponse
object
Get account transfer history
10 properties
OrderTimeInForceAsString
string
time in force can have the following string values "GTC", "FOK", "IOC", "GTX" (Good Till Crossing - for auction orders), see [details](/rest/general/order-type)
OrderStatusAsString
string
order status can have the following string values "OPEN", "CLOSED", "CANCELLED", "REJECTED"
TimeStampAsString
string
unsigned 64 bit integer value which is the number of milliseconds since EPOCH expressed as string
TradingAccountId
string
unique trading account ID
AssetSymbol
string
asset symbol as denoted in the world
Trade
object
18 properties 18 required
ClientOtcTradeId
string
unique numeric (i64) identifier generated on the client side expressed as a string value
Boolean
boolean
DerivativesSettlementResponse
object
Derivatives Settlement of one market for the trading account
13 properties
OrderSide
string
DateTime
string
ISO 8601 with millisecond as string
AssetValue
string
see [asset value](/rest/general/price-quantity-precision) format
OrderID
string
OrderHandle
string
Unique numeric (i64) identifier generated on the client side expressed as a string value
BorrowInterest
object
6 properties 6 required
OtcTradeId
string
unique numeric (i64) identifier generated on Bullish side expressed as a string value
UsdcValue
string
see [asset value](/rest/general/price-quantity-precision) format
QuoteAssetSymbol
string
asset symbol as denoted in the world
OtcMatchId
string
unique numeric (i64) identifier generated on Bullish side expressed as a string value
OrderStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bullish-history-api-openapi.yml Raw ↑

Other APIs Bullish publishes across the network.

Bullish Deprecated Features and APIs
AE Profile APIs.io
Bullish WebSocket Multi-Order Book API
AE Profile APIs.io
Bullish WebSocket Anonymous Trades API
AE Profile APIs.io
Bullish WebSocket Anonymous Ticks API
AE Profile APIs.io
Bullish WebSocket Auction Feed API
AE Profile APIs.io
Bullish WebSocket Index Data API
AE Profile APIs.io
Bullish WebSocket Private Data API
AE Profile APIs.io
Bullish FIX API
AE Profile APIs.io
Bullish Aggregator API
AE Profile APIs.io
Bullish Account Assets API
AE Profile APIs.io
Bullish Amm Instructions API
AE Profile APIs.io
Bullish Asset Data API
AE Profile APIs.io
#History
← Back to B APIs
API Details
ID
bullish:bullish-history-api
Base URL
https://api.exchange.bullish.com/trading-api
Docs
https://docs.exchange.bullish.com/rest/introduction
Provider
Bullish
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=bullish-history-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bullish-history-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Bullish History 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.