> For the complete documentation index, see [llms.txt](https://docs.bbx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bbx.com/bbx-dex-public-api/overview.md).

# Overview

This documentation describes the public market-data endpoints provided by **BBX DEX** for third-party market-data integrations.

BBX DEX provides separate integration endpoints for supported data platforms, including **CoinMarketCap** and **CoinGecko**. These integrations use the same underlying BBX market-data infrastructure, but their endpoint paths, field names, timestamp conventions, response formats, and eligible market coverage may differ.

Please refer to the relevant integration section for platform-specific endpoint definitions and response schemas.

The endpoints are:

* Read-only
* Publicly accessible
* Returned in JSON format
* Available without an API key, signature, login, authentication token, or custom request header

> Third-party platforms may ingest only the markets and instruments supported by their own listing and market-mapping systems.

***

### Base URL

```
https://dex.bbx.com
```

### Supported Integrations

BBX DEX currently provides public market-data endpoints for the following third-party integrations:

| Integration   | Current Market Scope   | API Prefix                                                       |
| ------------- | ---------------------- | ---------------------------------------------------------------- |
| CoinMarketCap | Spot and Futures       | `/sapi/v4/market/v1/public/cmc` and `/fapi/market/v1/public/cmc` |
| CoinGecko     | Cryptocurrency Futures | `/fapi/market/v1/public/coingecko`                               |

Each integration uses the same underlying BBX market-data infrastructure, but may use different endpoint paths, field names, timestamp conventions, response formats, and market-eligibility rules.

Refer to the relevant integration section for platform-specific endpoint definitions and response schemas.

***

### General Conventions

| Item               | Convention                                                                        |
| ------------------ | --------------------------------------------------------------------------------- |
| Authentication     | None                                                                              |
| Response format    | JSON                                                                              |
| Transport          | HTTPS                                                                             |
| Access type        | Public and read-only                                                              |
| Numeric precision  | Prices, volumes, rates, and other decimal values may be returned as strings       |
| Timestamps         | Returned as JSON integers; the applicable unit is documented for each integration |
| Market identifiers | Pair-naming conventions are documented in the relevant integration section        |

***

### Data Consistency

The public integration endpoints use the same underlying BBX market-data infrastructure as the BBX trading interface.

Platform-specific endpoints may use different field names, timestamp units, and response structures, but the underlying market data—including prices, trading volumes, order books, open interest, index prices, and funding rates—is sourced from BBX's market-data systems.

Minor timing differences may occur because the API and website update independently.

***

### Availability

The endpoints are designed to support regular automated market-data polling.

BBX may apply reasonable rate limits, traffic controls, or availability protections to maintain the stability of its public API services. These controls are intended to permit normal third-party market-data integrations.

***

### Documentation Sections

* CoinMarketCap Integration
* CoinGecko Integration
* Error Handling
* Data Integrity and Availability
* Changelog