CoinAPI is a high-performance platform that provides a unified API to access both real-time and historical cryptocurrency market data. It integrates data from a wide range of cryptocurrency exchanges, offering developers and institutions:

• A single access point for multiple exchange feeds
• Both raw and normalized (preprocessed) data
• Support for REST, WebSocket, FIX, and Flat File delivery
• Low-latency infrastructure for time-sensitive applications

CoinAPI simplifies access to digital asset data, making it easier for users to build trading algorithms, analytics platforms, and enterprise-grade applications without needing to manage separate exchange integrations.

Yes, CoinAPI offers custom subscription plans tailored to meet specific data requirements and business needs. If your organization requires specialized data sets, higher rate limits, or unique integration support beyond the standard subscription offerings, you can reach out to our sales team to discuss a customized solution.

Yes, subscription payments are executed automatically on your primary payment method when the subscription remains active.

Yes. Check the documentation for the output_format API parameter at https://docs.coinapi.io/market-data/rest-api#output-data-format (https://docs.coinapi.io/market-data/rest-api#output-data-format)

Yes, you may have multiple subscriptions.

Multiple subscriptions are commonly used when:

• The software is shipped to multiple third-party's by the customer (eg. self-hosted software)
• To separate environments inside the company (development, testing, staging, production)
• To separate multiple independent production sites (EUROPE, ASIA, etc)
• To separate multiple teams inside the company working on different features or products

Yes, please do!

1. Sign in on the GitHub
2. Fork our main GitHub repository: https://github.com/api-bricks/api-bricks-sdk (https://github.com/api-bricks/api-bricks-sdk)
3. Work on the changes and push them into your forked repository
4. When you are ready to share the changes with us. Create "Pull Request” to our main repository with a short description of the changes.

We no longer offer discounts for University/Non-profit/Research-only usage. We will be happy to speak with you to discuss your requirements and the best plan & pricing that will fit your needs! Contact us here: https://www.coinapi.io/contact-us (https://www.coinapi.io/contact-us)

Yes, we have a Status Page at: https://status.coinapi.io (https://status.coinapi.io/)

Yes, we do provide asset icons via REST API under the Metadata. More information can be found in our documentation here: https://docs.coinapi.io/market-data/rest-api/metadata/list-all-asset-icons (https://docs.coinapi.io/market-data/rest-api/metadata/list-all-asset-icons)

We do not support custom timezones, data is always processed in the UTC.

If you need to operate in the custom timezone then input and output values should be converted on the client-side before a request is sent to us or output data processed.

In the corner cases like OHLCV data on the higher than 1HRS periods (eg. 1DAY), you should execute queries only to the 1HRS period at the maximum and assemble higher periods like 1DAY on the client-side, as our 1DAY always starts and ends at the UTC midnight.

Yes, CoinAPI provides Service Level Agreements (SLAs) tailored specifically for enterprise clients. These SLAs define key performance and reliability metrics to support mission-critical applications, including:

• Guaranteed uptime and availability targets
• Maximum response time thresholds
• Dedicated support availability and escalation paths
• Incident response and resolution timelines

SLAs are structured to meet the needs of high-throughput trading platforms, institutional users, and large-scale data consumers who rely on consistent and predictable API behavior.

To discuss SLA options and terms, please contact our sales team at:

https://www.coinapi.io/contact-us (https://www.coinapi.io/contact-us)

You can generate an API Key via the Customer Portal. Once you have your API key, you can begin making requests immediately.

The actual integration time depends on the complexity of your project:

• For simple use cases, setup can take as little as 5 minutes
• For more complex systems (e.g., production-grade trading platforms or data pipelines), integration may take several days

Our SDKs, documentation, and sample code are designed to help accelerate the process, regardless of your environment or programming language.

Start here: (https://docs.coinapi.io/)https://docs.coinapi.io (https://docs.coinapi.io)

To stay informed about service status, outages, or scheduled maintenance, CoinAPI provides a dedicated status page:

Status Page: (https://status.coinapi.io/)https://status.coinapi.io (https://status.coinapi.io)

We recommend subscribing to email notifications directly on the page to receive real-time alerts.

If you encounter an issue that is not reflected on the status page or disagree with its current content, please report it using our support form:

Submit a request: https://support.apibricks.io/hc/en-us/requests/new (https://support.apibricks.io/hc/en-us/requests/new)

Yes, CoinAPI provides a standard Service Level Agreement (SLA) for all paid plans. This covers key performance metrics such as uptime, availability, and support responsiveness.

If your organization requires a custom SLA, this is available through our Enterprise Plan. Custom SLAs can include specific commitments around latency, incident response times, and dedicated infrastructure options.

To discuss custom SLA requirements, please submit a request here:

https://www.coinapi.io/contact-us (https://www.coinapi.io/contact-us)

Yes, your company should file a support ticket whenever an issue occurs. This is essential even if the problem seems temporary or intermittent.

Here’s why:

• Your support SLA (if applicable) is only activated when a ticket is submitted.
• Without a formal ticket, we cannot guarantee prioritization, investigation, or tracking of the issue.
• If your plan does not include a service-level SLA, we do not monitor or proactively respond to issues unless they are reported.

For customers with custom SLAs, we track specific metrics and build infrastructure to meet those guarantees. For all other users, we rely on incoming tickets to understand what matters to your business.

Our process:

• We continuously monitor infrastructure and act on system-level issues.
• However, without ticket input, we may not detect or be accountable for individual cases that affect your workflow.
• If needed, we expand monitoring and internal metrics based on patterns in submitted tickets.

To submit a ticket, use:

https://support.apibricks.io/hc/en-us/requests/new (https://support.apibricks.io/hc/en-us/requests/new)

CoinAPI delivers a comprehensive range of cryptocurrency market data across multiple formats and timeframes. The data includes both raw and aggregated market information from hundreds of supported exchanges.

Available data types:

• Metadata – Full metadata on supported trading pairs and instrument identifiers
• Exchange and asset information – Details about connected exchanges and tradable assets
• Quotes (Level 1) – Best bid/ask prices and sizes
• Order books (Level 2) – Full depth of market including all visible bids/asks
• Trades – Executed transaction data with price, size, and timestamp
• Exchange rates – Aggregated volume-weighted rates across markets
• OHLCV – Aggregated Open, High, Low, Close, and Volume data for timeframes starting at 1 second

This coverage supports a wide range of use cases—from algo trading and analytics to compliance, portfolio valuation, and backtesting.

Yes, CoinAPI offers integration assistance as part of our Enterprise Tier for the Market Data API and other services. This support can be tailored to your technical architecture, workflow requirements, and business objectives.

If you’re interested in hands-on onboarding, architecture reviews, or guided implementation, please contact our team to discuss the best setup for your use case.

Flat Files are usage-based. To start, create an account in the API BRICKS Console and add usage credits to your balance.
Once your balance is positive, create a Flat Files API key and start listing or downloading files through the S3-compatible API. Basic steps:

1. Log in or create an account at https://console.apibricks.io/.
2. Go to Billing → Add Usage Credits.
3. Create a Standard API Key and enable Flat Files API.
4. Use the Flat Files API docs to list and download the files you need.

Charges are deducted from your usage credits based on API calls and data transfer volume. New users can get $25 in free credits after payment verification and API key creation. Once you know your expected usage, you can stay on pay-as-you-go (metered) or move to a committed plan or Enterprise plan.

Yes, as stated on our legal terms under Customer Agreement section 2.4:

"You may terminate your initial Order of the applicable Software or Cloud Services under this Agreement, for no reason or any reason, by providing notice of termination. At your request (which may be made through your Account or by contacting us), we may disable the license key that allowed the Software to operate or disable access to the Cloud Services. All fees paid are non-refundable."

More information can be found here: https://www.coinapi.io/legal (https://www.coinapi.io/legal)

If your subscription was marked for cancelation using the customer portal and your billing period date has not passed, then you can still reactivate it by logging into the Customer Portal (https://console.coinapi.io/ (https://console.coinapi.io/)) and navigating to Subscriptions > Renew Subscription. You will be able to resume the subscription here.

If your subscription was marked for cancelation and your current billing period date has already passed, then you must acquire a new subscription from our Pricing page (https://www.coinapi.io/market-data-api/pricing (https://www.coinapi.io/market-data-api/pricing)).

Yes, bank and wire transfers are accepted, but only for annual subscriptions.

For monthly subscription plans, payment must be made via credit card through our secure Stripe checkout.

If you're interested in setting up an annual subscription via wire transfer, please contact our Support Team (https://support.coinapi.io/hc/en-us/requests/new) or Sales for invoicing assistance.

When signing up for a CoinAPI subscription, you may encounter payment errors returned by our payment processor, Stripe. Common examples include:

• balance_insufficient – Not enough funds on the card or account
• card_decline_rate_limit_exceeded – Too many decline attempts
• email_invalid – The email format is incorrect or unsupported by Stripe

How to resolve:

1. Refer to Stripe’s official error documentation for guidance:
   • Error codes: https://stripe.com/docs/error-codes#email-invalid (https://stripe.com/docs/error-codes#email-invalid)
   • Decline reasons: https://stripe.com/docs/declines/codes (https://stripe.com/docs/declines/codes)
2. If the error persists or you're unable to resolve it, please contact the CoinAPI support team here: https://support.coinapi.io/hc/en-us/requests/new (https://support.coinapi.io/hc/en-us/requests/new)

We’ll help you investigate and complete your sign-up.

Yes. CoinAPI offers customization through the Enterprise plan, which is fully adaptable to your technical, legal, and operational needs.

Custom options include:

• Dedicated account manager
• Custom onboarding and SLAs
• Premium support (including a dedicated Slack channel for $200/month)
• Flexible limits on API usage, request volume, and exchange coverage
• Tailor-made data delivery (e.g., custom S3 uploads, VPC peering, regional endpoints)

Add-ons:

• Business Plan users can also add a Slack support channel ($200/month)
• Additional data transfer is available at $1.25 per GB beyond the plan’s included 16 GB

To request a customized plan or explore upgrade options, contact CoinAPI Support (https://support.coinapi.io/hc/en-us/requests/new).

We build our own CDN network with nodes directly distributing data between each other via the fastest routes. Any existing CDN solutions are targeted on the caching which is not applicable to financial data.

Your sensitive information is stored inside the service provider, which is constantly audited and certified as a PCI-DSS Level 1 Service Provider. This is the most stringent level of certification available in the payments industry. To retain the certification, a payment provider must use world-class security tools and techniques to maintain a high level of security.

Flat Files is CoinAPI's service that delivers high-resolution, historical cryptocurrency market data in downloadable CSV format. This product is designed for users who require large-scale data access for offline processing, analytics, or backtesting.

Currently supported data types include:

• Trades
• Quotes
• Full Limit Order Book

These files are ideal for quant researchers, institutions, and analytics platforms that need to handle and analyze deep market data at scale.

Note:

OHLCV data is not included in the Flat Files offering. For time-aggregated candlestick data, please use the Market Data API or aggregate it yourself from trade data available in the Flat Files.

For documentation and pricing:

https://docs.coinapi.io/flat-files-api/

To minimize your API and data transfer costs when using CoinAPI’s Flat Files product, follow these proven strategies:

1. Target Specific Symbols or PairsDownload only the data relevant to your assets or strategies to reduce file volume and costs.
2. Use Efficient LIST CallsAvoid excessive listing operations. If you already know the exact file paths, skip listing and go straight to download.
3. Implement Delta DownloadsDownload only new or updated files since your last sync instead of fetching full datasets repeatedly.
4. Adjust Download FrequencyAssess how often you really need the data—daily downloads may be overkill for some use cases.
5. Cache LocallyStore previously downloaded data to avoid duplicate downloads and save on both credits and bandwidth.
6. Monitor & Review UsageUse the Customer Portal to review your API credit and data transfer consumption regularly.
7. Bundle DownloadsAutomate and schedule batch downloads during off-peak times or consolidate multiple symbols into fewer requests.

Bonus Tip: Use the Flat Files Estimator Script to forecast file sizes and costs before downloading.

CoinAPI's Flat Files product includes the following data types for in-depth historical analysis and low-latency backtesting:

1. QuotesTop-of-book data showing the best bid and ask prices and sizes.
   • Double timestamped (by exchange and server)
   • Useful for spread tracking, best-bid-offer (BBO) monitoring, and latency analysis
2. TradesEach entry represents a transaction between market participants, including price, size, and aggressor (if available).
   • Double timestamped
   • Ideal for tick-by-tick backtesting and execution analysis
3. Limitbook FullFull depth of book (L2 or L3 depending on the exchange), starting with a snapshot followed by all updates.
   • Suitable for reconstructing full market microstructure
   • Preferred by firms running complex simulation or queue analysis models

4. OHLCV (newly available)

• Open, High, Low, Close, and Volume bars
• Ready-to-use candlestick data for a wide range of assets and exchanges
• Saves engineering time compared to generating OHLCV client-side

Note:
Previously, OHLCV data was only available via the Market Data API. As of September 2025, OHLCV is now included directly in Flat Files.

For details on format, access, and billing, refer to the documentation:
Flat Files API Documentation

CoinAPI’s Flat Files are delivered in a standardized directory and file structure using CSV format, compressed with gzip for efficient storage and download.

Each file is structured as follows:

• File format: .csv.gz (CSV + GZIP compression)
• Directory structure: Organized by data type, date, exchange, and symbol
• Header row: Present in each CSV file for easy parsing
• Timestamps: Double-timestamped when applicable (exchange and receive time)

How to use the files:

1. Download the .csv.gz file using the Flat Files API or your preferred tool
2. Decompress it using a utility like gzip, 7-Zip, or similar
3. Load the CSV file into a spreadsheet, database, or processing script

For full file path patterns, schema definitions, and examples, visit the official documentation:

Data Types and File Structure Overview

CoinAPI provides multiple levels of support for users working with Flat Files:

• Documentation: Comprehensive technical documentation is available to guide you through file structure, usage, data types, billing, and access. Start here: Flat Files API Docs
• Support Portal: You can submit a ticket through our Support Portal for assistance with issues related to file access, API usage, data interpretation, or billing.
• Email Support: All plans include email support. For Enterprise plans, faster response times and custom support options (e.g., Slack channel) are available.
• Error Reporting: When submitting a ticket, include details such as file path, timestamps, exchange, and symbol involved to help us resolve your issue faster.

CoinAPI’s Flat Files provide access to high-resolution historical market data in CSV format. The available data types include:

• Trades – All executed trade events with price, size, and timestamp.
• Quotes – Best bid and ask updates (Level 1 order book).
• Full Order Book (limitbook_full) – Tick-by-tick updates of the order book at L2/L3 granularity.
• OHLCV (newly available) – Pre-aggregated candlestick data (Open, High, Low, Close, Volume) for multiple time intervals.

Flat Files support data going back to February 2014, depending on the exchange and symbol.

Note:
Previously, OHLCV was only accessible via the Market Data API. As of September 2025, OHLCV is also available directly through Flat Files for easier bulk download and analysis.

For details on format, access, and billing, see the documentation:
Flat Files API Documentation

CoinAPI offers extensive historical tick-level trade data through its Flat Files service—ideal for backtesting, quantitative modeling, and historical research.

Key availability by exchange:

• Binance – From July 14, 2017
• Coinbase Pro (GDAX) – From January 14, 2015
• Kraken – From January 7, 2014

Some legacy data extends back to July 2010, depending on the exchange.

To explore the full scope of available trade data across all supported venues, refer to our Flat Files API documentation, or reach out to support for assistance with a specific exchange or symbol.

Yes, CoinAPI’s Flat Files are fully normalized across all supported exchanges. Each dataset adheres to a consistent schema, regardless of the data source.

This unified format simplifies:

• Cross-exchange data analysis and backtesting
• Integration with internal systems and tools
• Elimination of exchange-specific parsing or mapping logic

For detailed information on the schema and data format, refer to the Flat Files API documentation, or contact support with specific questions.

Yes, CoinAPI guarantees schema consistency across all supported exchanges and historical periods. This ensures that your integrations remain stable over time and your historical analyses stay reliable as the dataset expands.

Key benefits:

• Standardized data structures for all venues and timeframes
• Synchronized timestamps across data types using high-precision time sync
• Confidence in accurate aggregation and comparison across exchanges

For technical specifications, refer to the Flat Files documentation or reach out to support.

Yes, CoinAPI uses standardized naming conventions for all symbols across its platform to ensure consistency and ease of integration, filtering, and analysis.

Symbol identifier patterns

CoinAPI defines symbol IDs using a structured pattern based on the instrument type:

• SPOT: {exchange_id}_SPOT_{asset_id_base}_{asset_id_quote}
• FUTURES: {exchange_id}_FTS_{asset_id_base}_{asset_id_quote}_{YYMMDD of future_delivery_time}
• OPTIONS: {exchange_id}_OPT_{asset_id_base}_{asset_id_quote}_{YYMMDD of expiration}_{strike_price}_{C/P}
• PERPETUALS: {exchange_id}_PERP_{asset_id_base}_{asset_id_quote}
• INDEXES: {exchange_id}_IDX_{index_id}
• CREDIT: {exchange_id}_CRE_{asset_id_base}
• CONTRACTS: {exchange_id}_COT_{contract_id}If duplicate IDs occur across markets, an additional suffix prefixed with _ is appended to ensure uniqueness.Variable namingAll variables follow the snake_case convention for improved readability and consistent usage across APIs and documentation.For further reference:
  • Flat Files API Naming Standards
  • Market Data API symbol metadata documentation.

CoinAPI’s Flat Files are built for seamless integration with cloud-native data infrastructures, thanks to the S3-compatible API and standardized format.

Key Integration Benefits

• S3-Compatible API: Fully interoperable with platforms like Amazon Redshift, Google BigQuery, Snowflake, and other data lakes or warehouses
• ETL-Ready: Works out of the box with major ETL tools (e.g., Apache NiFi, Airbyte, Fivetran)
• Language-Agnostic SDKs: Available in multiple languages with setup guides and working examples
• Optimized for Scale: Designed to support high-throughput batch ingestion of large historical datasets

Integration Overview

1. Review the Flat Files API documentation for endpoint structure and data format
2. Set up the relevant SDKs or S3-compatible client
3. Configure access credentials (e.g., AWS IAM roles or API keys)
4. Load data into your warehouse using standard ingestion pipelines

For advanced help, contact our support team to discuss architecture recommendations or troubleshooting tips.

Yes, CoinAPI provides official SDKs for a wide range of languages and ecosystems, making it easy to connect with your preferred data tools, platforms, and workflows.

Supported Languages and Frameworks

• Python, R, MATLAB
• Java, C++, C#.NET, Go, PHP
• JavaScript, TypeScript, Node.js
• Ruby, Objective-C, Haskell

These SDKs are well-suited for use with:

• Pandas and NumPy for in-memory data analysis
• Apache Spark for distributed data processing
• Apache Airflow for workflow automation and scheduling

Open Source & Ready to Use

Refer to the SDK Guide for each SDK to find installation steps, usage examples, and best practices.

Yes, CoinAPI offers both pull-based and automated sync mechanisms to keep your Flat Files data up to date.

Current: Pull-Based Access via S3-Compatible API

You can download Flat Files on demand using CoinAPI’s S3-compatible API, perfect for:

• Custom ingestion schedules
• Integration with existing S3 clients or scripts
• Incremental sync logic using directory metadata

Coming Soon: Push API (Self-Managed)

CoinAPI will soon offer a Push API feature that enables:

• Subscription to specific datasets
• Daily automatic delivery of updated files to your infrastructure
• Reduced manual effort and polling overhead

Available Now: Fully Managed Sync for Enterprise Plans

Enterprise customers can access an automated sync service that:

• Uploads Flat Files daily to a customer-owned S3 bucket
• Includes one-time bulk delivery and ongoing file updates
• Eliminates need for manual file handling

See the Flat Files API documentation for integration details or contact support for onboarding.

If a Flat File download fails or encounters integrity issues, CoinAPI’s S3-compatible API provides detailed diagnostics to help you detect and resolve the problem quickly.

Error Handling Mechanism

• HTTP status codes identify issues like missing files, permission errors, or network problems
• Amazon S3-style XML error messages provide structured responses for automated error handling in your ingestion pipeline

File Validation & Integrity

While CoinAPI does not currently expose checksums (e.g., MD5 or SHA) in public metadata:

• You can implement custom validation logic (e.g., file size thresholds or internal consistency checks)
• Consider logging and alerting for unexpected variations in file size or format

For mission-critical ETL workflows, adding a secondary validation layer is recommended.

Learn more about handling errors and file access in the Flat Files API documentation.

CoinAPI offers Service Level Agreements (SLAs) to ensure reliable access to both our REST API and Flat Files endpoints — tailored to your subscription level.

SLA Coverage Includes:

• Uptime guarantees for API and Flat File services
• Access reliability aligned with your plan tier
• Proactive system monitoring and fast response during incidents

Custom SLAs for Enterprise Clients

If you require strict performance guarantees, we offer custom SLA options as part of the Enterprise Plan. These may include:

• Higher uptime commitments
• Dedicated infrastructure
• Third-party-verified performance benchmarks
• Priority-level support and account management

To learn more, visit our Enterprise Plan page or contact our support team to discuss your SLA needs.

Flat Files are priced using a consumption-based model, determined by:

• API Calls Count – Every call to the Flat Files S3 API counts as one request
• Data Transfer – Charges are based on the amount of data you retrieve (measured in GB)

There are no per-user or seat-based fees. You only pay for what you use — making this model scalable for both light and heavy users.

For full pricing details and examples, refer to the Flat Files Pricing Page.

Yes — Flat Files are typically available after 00:00 UTC for the previous day's data. Availability may vary based on processing time and data volume.

• Most files are published by 06:00 UTC
• Lighter datasets are often available within a few hours after midnight

If your workflow depends on early access, we recommend setting your download window accordingly.

For timing details and current availability status, see the Flat Files API documentation.

When processing Full Limit Order Book (LOB) data from CoinAPI, updates reflect changes in market depth and liquidity. Here's how to handle key update types:

SUB / MATCH Updates

• If a SUB or MATCH update results in entry_sx (volume) being less than or equal to zero:→ Treat this as a DELETE event.→ Remove the order from your local order book.

This indicates that the order was either fully filled or canceled and no longer exists.

ADD Updates

• If an ADD update is received for a price level that already exists:→ Accumulate the entry_sx with the existing volume at that level.→ Do not replace the existing value, as you would with a SET.

This ensures your order book reflects the accurate aggregated depth at each price level.

If you're looking for detailed historical bid/ask data—including order book snapshots at specific times, CoinAPI has two key options:

Option 1: Flat Files (Best for Historical Access & Bulk Analysis)

• Full Limit Order Book (LOB) Data
  • Captures every change in the order book.
  • Allows you to reconstruct the full order book at any point in time.
• Quotes Data
  • Provides top-of-book data (best bid/ask prices) over time.
  • Lightweight and efficient for quick backtests or spread analysis.

Option 2: Market Data API (For Programmatic Access)

• All predefined plans include historical and live bid/ask and order book data.
• Choose based on your preferred access protocol:
  • REST API: Good for historical and filtered data
  • WebSocket: Best for real-time streaming
  • FIX API: Ideal for institutional trading setups

Recommendation:

• Use Flat Files for downloading a complete historical dataset.
• Use Market Data API if you want to integrate real-time bid/ask data with selective historical queries into your app or trading system.

To purchase and start using CoinAPI’s Flat Files (which include historical market data such as trades, quotes, and order books), follow these steps:

Step 1: Add Usage Credits

• Log in to your Customer Portal.
• Navigate to Billing > Add Usage Credits and fund your account using a credit card.
• To avoid running out of credits, enable Auto Recharge for automatic top-ups.

Step 2: Create an API Key for Flat Files

• Go to API Keys in the portal.
• Click Create Standard API Key.
• Disable access to all other products and enable only the Flat Files API.

Credits must be available in your account before you can access the Flat Files.

Step 3: List & Download Flat Files

• Refer to the Flat Files API documentation to explore the S3 API and list available files by exchange, symbol, and date.
• Optionally, estimate data transfer costs using our Data Transfer Estimation Script (this consumes credits, but you’ll receive $25 in free credits after verifying your payment method and generating an API key).
• When ready, download the data using the Download Object endpoint.

Tools Compatibility: The Flat Files API is S3-compatible, meaning you can use common tools like AWS CLI, boto3, or any compatible library or ETL tool for accessing and managing the data.

Billing: Charges are automatically deducted based on API usage and data transfer volume.

If you need assistance during setup, feel free to contact our support team.

The recommended method to retrieve Size and LastModified metadata for all symbols on a given exchange for a specific day is to perform a daily LIST call using a path prefix such as:

mathematicaT-TRADES/D-{`YYYYMMDD`}/E-HYPERLIQUID/

This method returns metadata for each file under that prefix, allowing you to:

• View file sizes
• Identify last modified timestamps
• Filter programmatically to isolate data for your target symbols

Note: Currently, there is no shortcut to retrieve Size or LastModified without listing the exact file paths.

For large-scale automations, consider batching LIST operations and filtering results client-side.

Currently, the only available options to retrieve metadata such as Key, Size, and LastModified for historical files in Flat Files are the standard S3-compatible operations: GET, LIST, and HEAD API calls. At this time, we do not provide a manifest file or a dedicated endpoint that allows you to query or fetch this metadata in a more cost-efficient or consolidated manner.

For the most accurate and up-to-date information, you must perform a LIST request to enumerate the available files under a given prefix. This allows you to see what data exists and then selectively GET or HEAD individual objects if you need additional metadata. While it may not minimize call volume in all cases, batching LIST requests strategically (e.g., by date range or exchange prefix) can help streamline the initial indexing process.

At this time, we do not have an estimated release date for when 1-minute OHLCV data will be available in the Flat Files S3 API under the T-OHLCV/ path. However, we’re actively working to expand our data types and this remains on our roadmap.

Once available, the OHLCV period (e.g., 1MIN) will be clearly indicated in the S3 file paths or filenames—typically encoded as part of the directory structure or filename convention. We’ll ensure that this follows a consistent pattern for easy parsing.

We’ll notify all users as soon as this data type becomes accessible.

Yes, you can purchase daily full-limit order book data for specific trading pairs such as AERGO-USD from the Coinbase exchange via our Flat Files product. This allows you to download bulk historical data without having to loop through API calls.

Alternatively, if you prefer using the Market Data API, you can access historical order book data using the date parameter. However, please note:

• If you're looking to retrieve data over a range of dates, each day must be requested individually—this applies to both API calls and Flat Files downloads.
• For API access, using the date parameter ensures the complete dataset for that specific day is retrieved.

For larger date ranges or bulk needs, Flat Files offer a more efficient and cost-effective approach.

Files are treated as the canonical historical dataset.