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

Bullet Trading API

The Trading API from Bullet — 2 operation(s) for trading.

Bullet Trading API is one of 9 APIs that Bullet 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 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 4 base URLs: /, https://tradingapi.mainnet.bullet.xyz, https://tradingapi.testnet.bullet.xyz, https://tradingapi.staging.bullet.xyz.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://tradingapi.bullet.xyz
Contact
License
Proprietary
Resource Areas
1

Paths & Operations 2

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

Trading 2
GET
/fapi/v1/openOrder
Query Current Open Order
query_open_order 5 params → 200400404500502
GET
/fapi/v1/openOrders
Query All Open Orders
query_open_orders 2 params → 200400404500502

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are BinanceOrder (27 properties), TpslLeg (6 properties), ApiErrorResponse (4 properties), PendingTpsl (3 properties). Each schema is shown below with its type and property counts.

BinanceOrder
object
27 properties 24 required
ApiErrorDetail
Typed details body. Variant order is important for untagged deserialization: keep the more-specific shape (JsonValidation) before more-permissive ones. Upstrea…
ApiErrorResponse
object
Structured API error response matching Bullet API format. All error responses from the trading API conform to this schema.
4 properties 2 required
TpslLeg
object
6 properties 6 required
JsonValidationErrorDetail
object
One JSON shape failure: machine-readable rule + full serde message including line/column. Surfaced under details on the wire.
2 properties 2 required
PendingTpsl
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bullet-trading-api-openapi.yml Raw ↑

Other APIs Bullet publishes across the network.

Bullet Account API
Bullet Address API
Bullet Health API
Bullet Market-Data API
Bullet Rollup API
Bullet SolanaOffchainTx API
Bullet Tx API
Bullet User Data (Beta) API
Where this information came from

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