Get started
Contact

Contact OHLC support
at [email protected].

OHLC is supported by email. Write to [email protected] about your account, billing, a data correction or an API question. There is no sales team and no phone line.

Get a free API key Read the quickstart

What to email us about

  • Account and API keys: sign-in problems, a key you need revoked, or access that does not match your plan.
  • Billing: charges, invoices, plan changes and cancellations. You can change or cancel a plan yourself in the billing portal; cancellation takes effect at the end of the paid period.
  • Data corrections: a price, dividend, split, filing or fact you believe is wrong or missing.
  • API questions: how an endpoint behaves, what a field means, or an error you cannot explain from the problem types.
  • Privacy requests: access, correction or deletion of your personal information, as described in the privacy policy.

What to include

Every API response, including errors, carries an X-Request-ID header. It is the fastest way for us to find your request. Please include:

  • The X-Request-ID value of the request in question.
  • The endpoint and query string, with your API key removed.
  • The symbol (MIC:TICKER, for example XNAS:AAPL) or instrument_id.
  • When you made the request, in UTC.
  • For an error, the code from the response body. For a data correction, the date, the value you expected and where you saw it.
Print the request ID of a callcURL
curl -s -D - -o /dev/null \
  'https://api.ohlc.io/v1/eod?symbols=XNAS:AAPL&from=2026-09-01&to=2026-09-30' \
  -H "Authorization: Bearer $OHLC_API_KEY" | grep -i x-request-id

Never send your API key by email. If a key has been exposed, revoke it in the dashboard and create a new one.

Check these first

  • GET /v1/datasets lists every dataset with its availability. Datasets marked unavailable return 501 dataset-unavailable by design until a source is connected. See datasets.
  • GET /v1/datasets/{dataset}/coverage reports how far back a dataset goes for your symbols, and any known gaps. See dataset coverage.
  • GET /v1/usage shows today's credit balance without spending credits. See credit usage and limits.
  • Each error links to its page under problem types, with the usual causes and fixes. The errors guide covers retries.

Reporting a security issue

OHLC publishes an RFC 9116 security contact at /.well-known/security.txt, and the same file at api.ohlc.io. It names [email protected]. Send the affected URL and the steps to reproduce, and do not access data that belongs to other accounts while testing.

Support by plan

Free is supported through the documentation. Developer, Pro and Commercial include email support, and Scale adds a dedicated channel on request. Anyone can write about account access, billing, privacy or security. We do not publish a response-time guarantee.

Questions, answered.

Is there a phone number or sales team?

No. OHLC is self-serve, and all support is by email at [email protected]. Plans are chosen and changed on the pricing page and in the dashboard.

How do I report wrong data?

Email [email protected] with the symbol, the date, the value you expected, where you saw it, and the X-Request-ID of the response that returned the value you believe is wrong.

How do I cancel my plan?

Cancel in the billing portal from your dashboard. Cancellation takes effect at the end of the current paid period. If you cannot reach the portal, email support.

Why does a dataset return 501 or 503?

A 501 dataset-unavailable means no source is connected to that dataset yet; retrying will not change the answer. A 503 dataset-unavailable means the dataset has a source but nothing published for your markets yet. /v1/datasets shows which datasets are available.

A little JSON.
A lot of possibility.

Explore the API