# Build Python Exchange Integrations with CCXT

Cryptocurrency exchanges expose different APIs for market data, account access, and trading. This skill guides Python integrations through CCXT examples for REST requests and WebSocket streams.

## Install

```bash
npx skillstore add ccxt/ccxt-python
```

## Metadata

- Status: approved
- Slug: ccxt-ccxt-python
- Skillstore revision: r1
- Version status: missing
- Tree hash: 10582297be943eaf6b9c0ffc62656d0bb11ee78fc26788782cac9d646710657c
- Author: ccxt
- GitHub username: ccxt
- Repository: https://github.com/ccxt/ccxt/tree/931253cb510e51642ccf7b225c2acf66fe5823ca/.claude/skills/ccxt-python
- Ref: c993c6abcbffafea2683d7748b53b3dfaf438415
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 63
- Public page: https://skillstore.pages.dev/skills/ccxt-ccxt-python
- Manifest: https://skillstore.pages.dev/api/skills/ccxt-ccxt-python/manifest

## Capabilities

- Explain CCXT installation and synchronous or asynchronous exchange initialization.
- Provide REST examples for tickers, order books, balances, orders, and trade history.
- Guide real-time ticker, order book, trade, and account subscriptions with CCXT Pro.
- Explain environment-based authentication, rate limiting, capability checks, and exchange error handling.
- Describe order-router queries, dry runs, execution plans, idempotency, and optional safety limits.
- Document prediction-market outcome handles and Bitget stock-routing distinctions.

## Use Cases

- Collect exchange market data: Use REST requests to retrieve tickers, order books, and historical candles for Python research workflows.
- Develop trading integrations: Structure exchange authentication, order handling, rate limits, and error recovery before testing with controlled permissions and amounts.
- Monitor portfolio changes: Combine authenticated balance subscriptions with live market streams for account monitoring without enabling order placement.

## Prompt Templates

### Beginner: Fetch a public ticker

```
Show a synchronous Python CCXT example that loads Binance markets and fetches BTC/USDT. Enable rate limiting and use no credentials or trading methods.
```

### Intermediate: Stream market updates

```
Create an asyncio CCXT Pro ticker monitor for BTC/USDT and ETH/USDT. Check exchange support, handle network errors, and close connections in finally blocks.
```

### Advanced: Monitor private balances

```
Design a read-only Python balance monitor using named environment variables. Check permissions, handle authentication failures, and keep secrets and account details out of logs.
```

### Expert: Review a router execution plan

```
Design a Python order-router dry run with a stable request identity, positive notional and plan-age limits, and unknown-outcome handling. Do not enable live execution.
```

## Limitations

- This is a documentation skill, not a bundled trading service; CCXT installation and exchange access are separate requirements.
- Method availability, permissions, market limits, and exchange behavior must be checked for each integration.
- Some reference sections contain JavaScript syntax and camelCase examples that need adaptation for Python.
- The documented Python order router is synchronous and does not implement watch\_route streaming.

## Best Practices

- Use narrowly scoped exchange credentials from environment variables and redact all shared diagnostics.
- Check exchange capabilities and market limits; enable rate limiting and close asynchronous clients in finally blocks.
- Test with dry runs or supported sandboxes; require approval, spending limits, freshness checks, and stable identities before live trading.

## Anti Patterns

- Paste real API secrets into prompts, source files, or diagnostic logs.
- Run live order examples without approval, spending limits, or market validation.
- Retry an order with an unknown outcome before checking the venue for an existing order or fill.

## Security Audit

- Audited at: 2026-11-07T14:39:45.17\+00:00
- Summary: All 419 static findings are false positives involving Markdown, reference URLs, proxy placeholders, exchange authentication, or financial API terminology. Two documentation risks remain: live routing without spending or freshness limits, and raw diagnostics without redaction guidance. No evidence found of prompt injection, hidden command execution, or intentional credential exfiltration in the reviewed file.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0