# Common Issues

## Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you've copied the full API key without any leading or trailing spaces. If you're using a RapidAPI-hosted Yahoo Finance API, make sure your subscription to that specific API is active — having a RapidAPI account alone isn't enough. You also need to verify that your plan hasn't exceeded its monthly request quota.

</details>

<details>

<summary>The data flow fails immediately after I run it</summary>

This usually means the API key is invalid or the API endpoint is unreachable. Try pasting your key into the provider's own test console to confirm it's working, then re-enter it in Coupler.io.

</details>

## Missing data

<details>

<summary>No data is returned for my selected interval and date range</summary>

Certain interval and date range combinations are not supported by Yahoo Finance. Specifically, short intervals like `1m` or `5m` are only available for very recent periods (typically 7 days or less). If you select `1m` with a `1y` range, the API will return nothing. Switch to a longer interval (e.g., `1d`) or a shorter date range (e.g., `7d`) for intraday data.

</details>

<details>

<summary>Some dates are missing from the results</summary>

Yahoo Finance does not return data for market holidays, weekends, or trading halts. Gaps in the data for those dates are expected and not a Coupler.io issue.

</details>

<details>

<summary>One of my tickers returns no data</summary>

Verify the ticker symbol is correct and that the security is still actively traded. Delisted stocks or tickers that have changed symbols (e.g., after a merger) may return empty results. Try looking up the exact symbol on Yahoo Finance directly before adding it to your data flow.

</details>

## Permission errors

<details>

<summary>I'm getting a 403 or "forbidden" error</summary>

This usually means your API plan does not have access to the endpoint Coupler.io is calling. Check whether your RapidAPI subscription tier includes historical data or the interval you've selected — some free tiers restrict access to certain endpoints.

</details>

## Data discrepancies

<details>

<summary>The Adjusted Close values changed between two pulls</summary>

This is expected behavior. Adjusted Close is recalculated retroactively whenever a stock split or dividend is announced. If you need a stable historical record, store a snapshot of each pull rather than overwriting previous data.

</details>

<details>

<summary>Prices don't match what I see on Yahoo Finance's website</summary>

Yahoo Finance may display prices with a 15-minute delay for some markets during live trading hours. The API data may also differ slightly from the website display due to post-market adjustments. For end-of-day analysis, always use the daily close from the previous completed session.

</details>

## Rate limits

<details>

<summary>I'm hitting rate limit errors when pulling many tickers</summary>

If you're querying a large number of tickers in one data flow, you may exceed the requests-per-minute or requests-per-month limit of your API plan. Consider splitting tickers across multiple data flows or upgrading your API plan. You can use Coupler.io's **Append** transformation to merge results from separate data flows into one destination table.

</details>