> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/coin-api.md).

# Coin API

Connect Coin API to Coupler.io for real-time and historical crypto market data — OHLCV candles, trades, and quotes across thousands of exchange pairs.

Coin API is a financial data provider that delivers historical and real-time cryptocurrency market data — including price candles, individual trades, and bid/ask quotes — across thousands of trading pairs and exchanges. Connect it to Coupler.io to pull structured crypto market data directly into your analytics tools or AI assistants without writing a single line of code.

## Why connect Coin API to Coupler.io?

* **Centralize crypto market data** — pull OHLCV candles, raw trades, and quote data into one place for unified analysis
* **Automate historical pulls** — schedule recurring data flows to keep your dashboards and models up to date
* **Combine multiple symbols or entities** — use Append or Join transformations to analyze several trading pairs side by side
* **Send data to AI tools** — pipe market data directly into ChatGPT, Claude, Gemini, or Perplexity for pattern analysis and summaries

## Prerequisites

* A Coin API account with an active API key ([get one at coinapi.io](https://www.coinapi.io/))
* The Symbol ID for the trading pair you want to pull data for (e.g., `BITSTAMP_SPOT_BTC_USD`) — find the full list in the [Coin API docs](https://docs.coinapi.io/#list-all-symbols-get)
* A Coupler.io account

## Quick start

{% hint style="success" %}
Start with the **OHLCV Historical Data** entity using a single well-known symbol like `BITSTAMP_SPOT_BTC_USD` to verify your connection before pulling data for multiple pairs.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Go to your Coupler.io dashboard and click **Add data flow**. Search for **Coin API** and select it as your source.
{% endstep %}

{% step %}
**Enter your Coin API key.** Paste your API key into the authentication field. You can find or generate your key in the [Coin API dashboard](https://www.coinapi.io/dashboard) under your account settings.
{% endstep %}

{% step %}
**Select an entity.** Choose one of the three available entities: OHLCV Historical Data, Trades Historical Data, or Quotes Historical Data.
{% endstep %}

{% step %}
**Configure your parameters.** Enter the Symbol ID for your trading pair, set a time interval (for OHLCV), and use the date pickers to define your start and end dates. Set a record limit if needed (default is 100, max is 100,000).
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual run and confirm that data loads correctly before setting up a schedule.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                 | Description                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------- |
| OHLCV Historical Data  | Open, High, Low, Close, and Volume candles for a trading pair over a chosen time interval |
| Trades Historical Data | Individual trade transactions with price, volume, and timestamp                           |
| Quotes Historical Data | Historical bid and ask price quotes with timestamps                                       |

## Coin API data overview

Coin API gives you access to three types of historical cryptocurrency market data. Each entity focuses on a different level of market detail — from aggregated candles to tick-level trades and quotes.

## Entities

| Entity                 | Best for                                                      |
| ---------------------- | ------------------------------------------------------------- |
| OHLCV Historical Data  | Price trend analysis, charting, backtesting strategies        |
| Trades Historical Data | Execution analysis, volume profiling, microstructure research |
| Quotes Historical Data | Spread analysis, liquidity research, bid/ask dynamics         |

## OHLCV Historical Data

#### Metrics

| Field           | Description                                                 |
| --------------- | ----------------------------------------------------------- |
| `price_open`    | Opening price at the start of the period                    |
| `price_high`    | Highest price during the period                             |
| `price_low`     | Lowest price during the period                              |
| `price_close`   | Closing price at the end of the period                      |
| `volume_traded` | Total volume of the base asset traded during the period     |
| `trades_count`  | Number of individual trades that occurred during the period |

#### Dimensions

| Field               | Description                                                 |
| ------------------- | ----------------------------------------------------------- |
| `symbol_id`         | The trading pair identifier (e.g., `BITSTAMP_SPOT_BTC_USD`) |
| `time_period_start` | Start timestamp of the candle period                        |
| `time_period_end`   | End timestamp of the candle period                          |
| `time_open`         | Exact timestamp of the first trade in the period            |
| `time_close`        | Exact timestamp of the last trade in the period             |

## Trades Historical Data

#### Metrics

| Field   | Description                     |
| ------- | ------------------------------- |
| `price` | Execution price of the trade    |
| `size`  | Volume of the base asset traded |

#### Dimensions

| Field           | Description                                      |
| --------------- | ------------------------------------------------ |
| `symbol_id`     | The trading pair identifier                      |
| `time_exchange` | Timestamp reported by the exchange               |
| `time_coinapi`  | Timestamp recorded by Coin API                   |
| `uuid`          | Unique identifier for the trade                  |
| `taker_side`    | Side of the taker (buy or sell, where available) |

## Quotes Historical Data

#### Metrics

| Field       | Description                                    |
| ----------- | ---------------------------------------------- |
| `ask_price` | Best ask (sell) price at the time of the quote |
| `ask_size`  | Volume available at the ask price              |
| `bid_price` | Best bid (buy) price at the time of the quote  |
| `bid_size`  | Volume available at the bid price              |

#### Dimensions

| Field           | Description                        |
| --------------- | ---------------------------------- |
| `symbol_id`     | The trading pair identifier        |
| `time_exchange` | Timestamp reported by the exchange |
| `time_coinapi`  | Timestamp recorded by Coin API     |

## Common metric combinations

* **OHLCV + volume\_traded + trades\_count** — identify high-activity periods where price moved on large volume
* **Quotes: ask\_price - bid\_price** — calculate spread over time to measure market liquidity
* **Trades: price + size** — compute volume-weighted average price (VWAP) across a session
* **OHLCV across multiple symbols** — use the **Append** transformation to combine candle data from different trading pairs for cross-asset comparison

## Use cases by role

{% tabs %}
{% tab title="Quant analysts" %}

* Pull OHLCV data for multiple symbols and use **Append** to build a unified price history table for backtesting
* Calculate rolling volatility and Sharpe ratios directly in BigQuery or a connected spreadsheet
* Use trades data to analyze execution slippage and fill quality
  {% endtab %}

{% tab title="Finance teams" %}

* Track portfolio asset prices over custom date ranges and export to Excel or Google Sheets for reporting
* Monitor bid/ask spreads from quotes data to assess liquidity risk for crypto holdings
* Schedule daily OHLCV pulls to maintain an up-to-date price ledger
  {% endtab %}

{% tab title="Researchers & AI users" %}

* Pipe OHLCV or trades data into ChatGPT, Claude, or Gemini to detect patterns and generate plain-language market summaries
* Use Perplexity or OpenClaw to ask questions directly over your historical trade data
* Combine multiple entities with **Join** to enrich trade records with contemporaneous quote data
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Symbol IDs are exchange-specific — `BITSTAMP_SPOT_BTC_USD` and `COINBASE_SPOT_BTC_USD` are different symbols even for the same asset pair
* The time interval (period) parameter only applies to OHLCV data — trades and quotes return tick-level records
* Leaving the end date empty will pull data up to the current time, which is useful for scheduled incremental flows
* Very short time intervals (e.g., 1-second candles) over long date ranges can produce millions of rows — use the record limit parameter to control output size
* Coin API's free tier has rate limits and a cap on historical data depth; paid plans unlock full historical coverage

## Coin API common issues

### Connection issues

<details>

<summary>My API key is rejected or I see an authentication error</summary>

Double-check that you copied the full API key from your [Coin API dashboard](https://www.coinapi.io/dashboard) with no leading or trailing spaces. Free-tier keys are valid but have usage restrictions — if your key has expired or exceeded its quota, generate a new one from your account settings.

</details>

<details>

<summary>The data flow fails immediately after setup</summary>

This usually means the Symbol ID is invalid or formatted incorrectly. Symbol IDs are case-sensitive and exchange-specific (e.g., `BITSTAMP_SPOT_BTC_USD`). Check the [Coin API symbol list](https://docs.coinapi.io/#list-all-symbols-get) to confirm the exact ID for your trading pair.

</details>

### Missing data

<details>

<summary>My data flow returns zero rows</summary>

Check three things: (1) The Symbol ID exists and has data for your selected date range. (2) Your start and end dates are set correctly using the date pickers — a reversed date range will return nothing. (3) Your record limit isn't set to 0. The default is 100, so if you've accidentally entered 0, no records will be returned.

</details>

<details>

<summary>Data stops before my specified end date</summary>

You've likely hit the record limit cap. The maximum is 100,000 records per request. If your combination of symbol, interval, and date range produces more records than the limit allows, the pull will stop early. Narrow your date range or use a larger time interval (e.g., switch from 1-minute to 1-hour candles) to reduce the row count.

</details>

<details>

<summary>Some time periods have gaps in OHLCV data</summary>

Gaps usually reflect periods of no trading activity on that specific exchange for that symbol. This is expected behavior — Coin API only records candles where trades actually occurred. If you need a gap-filled series, you'll need to handle that downstream in your destination (e.g., in BigQuery or a spreadsheet formula).

</details>

### Permission errors

<details>

<summary>I get a 403 error when pulling historical data</summary>

Free-tier Coin API accounts have restricted access to historical data — typically limited to the past 30 days. A 403 on historical requests usually means your plan doesn't cover that date range. Upgrade your Coin API subscription or adjust your start date to fall within your plan's allowed window.

</details>

### Data discrepancies

<details>

<summary>Prices don't match what I see on a trading exchange's website</summary>

Coin API aggregates data from specific exchange feeds. Make sure your Symbol ID matches the exact exchange you want (e.g., `BINANCE_SPOT_BTC_USDT` vs. `COINBASE_SPOT_BTC_USD`). Price differences between exchanges are normal due to arbitrage gaps and liquidity differences.

</details>

### Rate limits

<details>

<summary>My data flow is throttled or returns rate limit errors</summary>

Coin API enforces rate limits based on your subscription tier. If you're running multiple data flows against the same API key simultaneously, requests can stack up and trigger throttling. Stagger your data flow schedules or reduce the number of concurrent flows. If you consistently hit limits, consider upgrading your Coin API plan.

</details>

## Coin API FAQ

<details>

<summary>What is a Symbol ID and how do I find the right one?</summary>

A Symbol ID uniquely identifies a trading pair on a specific exchange. The format is typically `EXCHANGE_TYPE_BASEASSET_QUOTEASSET` — for example, `KRAKEN_SPOT_ETH_USD` means ETH/USD spot on Kraken. You can browse the full list of valid Symbol IDs in the [Coin API documentation](https://docs.coinapi.io/#list-all-symbols-get). Always copy the exact ID — they're case-sensitive.

</details>

<details>

<summary>Can I pull data for multiple trading pairs in one data flow?</summary>

Each data flow is configured for a single Symbol ID. To analyze multiple pairs together, create a separate data flow for each symbol and then use the **Append** transformation in Coupler.io to merge them into one unified dataset before loading to your destination.

</details>

<details>

<summary>What time intervals are available for OHLCV data?</summary>

Coin API supports a wide range of periods — from 1 second up to 1 year. Common options include `1SEC`, `1MIN`, `5MIN`, `15MIN`, `1HRS`, `1DAY`, and `1MTH`. The full list is available in the [Coin API periods documentation](https://docs.coinapi.io/#list-all-periods-get). Note that the period parameter only applies to the OHLCV entity — trades and quotes are always tick-level.

</details>

<details>

<summary>How many records can I pull per request?</summary>

The default record limit is 100 and the maximum is 100,000 per request. If your date range and interval combination produces more rows than your limit allows, the data will be truncated at the limit. Adjust your date range, use a larger interval, or split the pull across multiple flows to work around this.

</details>

<details>

<summary>Does a free Coin API account give me access to full historical data?</summary>

No. Free-tier accounts typically have restricted access to historical data depth — often limited to the past 30 days. Requests for older data will return a 403 error. You'll need a paid Coin API plan to access extended historical coverage.

</details>

<details>

<summary>Can I send Coin API data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can pipe OHLCV or trades data directly into these tools to ask questions, generate summaries, or identify patterns in your market data.

</details>

<details>

<summary>What's the difference between time_exchange and time_coinapi in trades and quotes data?</summary>

`time_exchange` is the timestamp that the exchange itself reported for the event, while `time_coinapi` is when Coin API received and recorded it. For most analysis, `time_exchange` is the more accurate reference for when a trade or quote actually occurred. Differences between the two reflect network and processing latency.

</details>

{% hint style="info" %}
For details on what fields are returned by each entity, see the [Data Overview](#coin-api-data-overview). For help with errors or missing data, check [Common Issues](#coin-api-common-issues).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/coin-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
