TickAtlas
Documentation

Build with TickAtlas. From first request to production.

Ordinary HTTP, API-key authentication and JSON responses. Start with one endpoint, then add economic events, 42 indicator series, screeners, historical data or streaming as your application grows.

Start the quickstart Browse the API reference
X-API-Key header Consistent error objects Python, JavaScript, PHP, Go
docs · quickstart
01 · first request

Your first authenticated call

One header, one endpoint. The response shape below is the same one every endpoint returns.

GET /v1/indicator?symbol=EURUSD&indicator=RSI_14&timeframe=H1
X-API-Key: YOUR_API_KEY
AuthX-API-Key header
SDKs4 official languages
NextReference → production
Three ways in

Start with what you are trying to ship.

The docs are organised by intent rather than by module, so you can go straight to the task in front of you.

Get a first response

One authenticated GET, a JSON body you can read, and the shape every other endpoint follows.

Quickstart · 5 minutes

Find the exact contract

Per-endpoint parameters, response schemas and error codes for everything under /v1.

API reference

Ship it to production

Rate limits, retries, error handling and the things that bite once real traffic arrives.

Rate limits · Errors · SDKs
Quickstart

From API key to useful data in three steps.

01

Create an account

Signup mints an API key and $2.50 of starting credit. No card required.

02

Send the header

Every request carries X-API-Key. There is no OAuth dance and no token refresh.

03

Read the envelope

Responses share one shape, so the parsing you write once works across the API.

/v1/indicator 
curl -H "X-API-Key: YOUR_API_KEY" \
  "https://tickatlas.com/v1/indicator?symbol=EURUSD&indicator=RSI_14&timeframe=H1"
{
  "symbol": "EURUSD",
  "timeframe": "H1",
  "indicator": "RSI_14",
  "value": 58.4
}
Documentation map

Everything has a clear home.

Four groups, no hunting. Each entry says how long it takes to read.

Getting started

Authentication, quotas, and how to talk to the API correctly.

Start here
Authentication API keys, headers, and security best practices 3 min Rate Limits Understand usage quotas and rate limiting by plan 4 min Error Handling HTTP error codes, error response format, and troubleshooting 5 min

Core reference

Client libraries, change log, and what to check when something looks off.

Reference
SDKs & Libraries Official client libraries for Python, JavaScript, PHP, and Go 3 min Changelog API version history and breaking changes 2 min Troubleshooting Common issues, error diagnosis, and step-by-step fixes 5 min

Specialized endpoints

Endpoint-specific deep dives beyond the standard REST shape.

Deep dive
Economic Calendar Calendar API endpoint: parameters, response format, and polling strategies 5 min

Integrations

Drop the API into a low/no-code automation pipeline.

No-code
Zapier Integration Connect live Forex data to 5,000+ apps via Zapier Webhooks 5 min n8n Integration HTTP Request node setup for n8n workflows and alert pipelines 5 min
API surface

Jump straight to the contract you need.

The badge on each card is its weight: what one call costs in pay-as-you-go credit units. Every call counts once against a daily quota.

GET 1x
/v1/indicator

Single indicator value
GET 1x
/v1/indicators

All indicators for symbol
GET 5x
/v1/summary

Rule-based market analysis
GET 2x
/v1/ohlc

OHLCV candlestick data
GET 2x
/v1/screener

Market screening
GET 2x
/v1/multi

Multi-symbol batch
GET 2x
/v1/calendar

Economic calendar events
GET 1x
/v1/quote

Live bid/ask prices
GET 1x
/v1/spread

Spread analysis
GET 3x
/v1/ticks

Raw tick data
GET 2x
/v1/heatmap

Currency strength
GET 1x
/v1/sessions

Market session status
GET 1x
/v1/symbols

Available instruments
SDKs

Use HTTP directly, or let the client library handle the plumbing.

Nothing in the API requires an SDK — it is plain REST. The official clients exist to wrap authentication, retries and pagination so you do not write them again.

Python pip install tickatlas Docs →
JavaScript npm install tickatlas Docs →
PHP composer require tickatlas/sdk Docs →
Go go get github.com/tickatlas/go Docs →
Production readiness

From 200 OK to production.

The six things that separate a working prototype from an integration that survives real traffic.

Throughput

Respect the rate limit

Limits are per-key and per-minute. A 429 carries the window so you can back off precisely.

Failure

Handle errors explicitly

Error objects are consistent across endpoints. Treat the code, not the message, as the contract.

Clients

Use an SDK or plain HTTP

The SDKs wrap auth and retries. Nothing in the API requires them.

Secrets

Keep keys server-side

A key in browser JavaScript is a public key. Proxy through your own backend instead.

Change

Watch the changelog

Breaking changes are versioned and announced there before they land.

Diagnosis

Check troubleshooting first

Most integration problems are one of a handful of documented causes.

Something not working?

Start with troubleshooting — most integration problems are one of a handful of documented causes. If it is not there, contact us with the request and the error body.

Troubleshooting Contact support

Platform status

Live availability for the API, the data pipeline and the Market Monitor.

Open status page
Status is published on /status
Start building

Start with one request. Scale from there.

Create an account, send one authenticated GET, and add the rest of the platform as your application needs it.

Open the quickstart API reference