CryptoHFTData developer resources

Build with the CryptoHFTData API

Start in the zero-auth read-only sandbox with public discovery and rate-limited downloads, or create a free account and generate an API key yourself. The stable v1 REST surface, typed OpenAPI contract, Python package, CLI, bulk-file guides, MCP metadata, and agent skills are linked below.

Quick start for agents and developers

1. DiscoverCall GET https://api.cryptohftdata.com/v1/symbols with an exchange and data type, or inspect the browser data explorer. No API key is required.
2. Authenticate when usefulUse the 60-request-per-minute anonymous download tier, or sign up and generate a key immediately for sustained workflows. No sales contact or credit card is required.
3. Download safelyCheck status, construct the exact hourly archive path, honor RateLimit and Retry-After headers, and preserve that path with your research output.

Official CryptoHFTData developer resources

OpenAPI 3.1 specification

Typed operations, parameters, success responses, and error schemas for the stable v1 REST API.

REST API documentation

Human-readable endpoint guides, examples, authentication, symbols, and dataset-specific requests.

Authentication and API keys

Create a free account, generate your key without sales assistance, and mint short-lived bearer tokens.

Zero-auth API sandbox

Test production-compatible status, symbol discovery, typed errors, and rate-limited downloads without credentials.

Python SDK and CLI

Install the official cryptohftdata package from PyPI for Python workflows and the cryptohftdata command-line tool.

Flat-file and bulk access

Read archive paths directly or obtain temporary credentials for bulk research workflows.

MCP server card

Discover public MCP tools for status, exchange coverage, and download examples.

Agent skills

Machine-readable workflows for downloads, exchange discovery, and ingestion checks.

llms.txt

Canonical context, when-to-use guidance, call patterns, and links for software agents.

Versioning, deprecation, errors, and rate limits

Versioning: integrate with https://api.cryptohftdata.com/v1. Breaking contract changes receive a new major URL. Existing unversioned routes are compatibility aliases.

Deprecation: when a stable operation is scheduled for removal, CryptoHFTData documents the replacement and sends Deprecation, Sunset, and migration Link headers at least 180 days before shutdown.

Errors: JSON failures use a human-readable error and, where available, a stable machine-readable code. Typed error responses are defined in OpenAPI.

Rate limits: anonymous downloads allow 60 requests per client IP in a fixed 60-second window. Read RateLimit, RateLimit-Policy, RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset on responses; wait for Retry-After after a 429. Authenticated limits may differ.