OHLC API Rate Limits and Errors

Public request limits

No API key is required for the public tier. The limits apply to the OHLC and data quality endpoints.

Rate limit headers

Error codes

Best practices for large pulls

• Cache successful responses locally instead of requesting the same range twice.
• Split multi-year M1 requests into monthly windows.
• Use higher timeframes when you do not need tick-sensitive bars.
• Respect Retry-After on 429; do not use a tight retry loop.
• Treat 413 as a request design problem, not a transient error.
• Keep your client timeout above the expected response time for large JSON payloads.

Request examples

curl -I "https://www.algospecial.com/api/ohlc.php?symbol=XAUUSD&tf=M15&from=2026-01-01&to=2026-01-31"

import time
import requests

url = "https://www.algospecial.com/api/ohlc.php"
params = {
    "symbol": "EURUSD",
    "tf": "M15",
    "from": "2026-01-01",
    "to": "2026-01-31",
}

for attempt in range(3):
    r = requests.get(url, params=params, timeout=30)
    if r.status_code != 429:
        r.raise_for_status()
        print(r.json()["rows"])
        break
    time.sleep(int(r.headers.get("Retry-After", "60")))
else:
    raise SystemExit("Rate limit retry exhausted")

# Instead of a multi-year M1 request, use H1 for lower-volume research.
curl "https://www.algospecial.com/api/ohlc.php?symbol=XAUUSD&tf=H1&from=2025-01-01&to=2025-12-31"

All timestamps are broker server time. Some legacy forex exports return 0 for TickVolume and Spread because those fields were not present in the source feed.

Related API guides