TickAtlas

Node.js Trading API — async/await Native

Use the built-in fetch() — no SDK required. Drop into Discord.js bots, Express middleware, Next.js API routes, or serverless functions.

Get $2.50 free credit
No credit card$2.50 PAYG credit on sign up
15+API endpoints
42Indicator series
M1–D17 timeframes
$2.50PAYG starting credit
Why TickAtlas

Why Use TickAtlas?

Pre-Calculated, Redis-Cached

Indicator values are computed server-side on every new candle. Your app queries the result — no TA library, no candle history needed.

7 Timeframes

M1, M5, M15, M30, H1, H4, D1 — the same endpoint serves scalpers and position traders alike.

Forex, Crypto, Commodities

EURUSD, GBPUSD, XAUUSD, BTCUSD, USDJPY — data available for every symbol in our data.

One Request. Instant Data.

REQUEST 
const res = await fetch(
  "https://tickatlas.com/v1/indicator?symbol=EURUSD&indicator=RSI_14&timeframe=H1",
  { headers: { "X-API-Key": "YOUR_API_KEY" } }
);
const { data } = await res.json();
console.log(`RSI: ${data.value}`);

Three Code Examples

fetch() Node 18+ · zero dependencies
axios Parallel multi-symbol scan
Discord.js Slash command /rsi EURUSD H1

Where to Deploy Your Node.js Bot

Serverless Functions

Deploy to Vercel, Netlify, AWS Lambda, or Cloudflare Workers. A single async function that calls TickAtlas and returns a result runs perfectly in a serverless context.

VPS or Railway

Run a persistent Node.js process with setInterval() for scheduled polling. Railway.app has a free tier that keeps your bot running 24/7 with zero DevOps.

Express / Fastify Backend

Build a market data proxy that your frontend calls. The Express backend fetches from TickAtlas, caches results, and serves your own users — with your own rate limiting and branding.

Compatible JavaScript runtimes and frameworks

Node.js 18+ Deno Bun Discord.js Express Fastify Next.js Remix Cloudflare Workers Vercel Edge

Plug into any stack

  • ChatGPT Custom GPTs
  • Claude Tools
  • Python / pandas
  • Node.js
  • Discord bots
  • Slack webhooks
  • n8n
  • Zapier
  • Google Sheets
Pricing

Start on pay-as-you-go, upgrade when the traffic justifies it.

Every new account starts with $2.50 of pay-as-you-go credit and no card. Monthly plans add a flat monthly price, WebSocket streaming and support.

Pay as you go
$2.50 credit No card required to start
  • $2.50 of credit included
  • Every REST endpoint except raw ticks
  • No card required, no overage
  • 10 API keys
See plan details
Starter
$29 per month · 10,000 requests/day · 120/min
  • Every REST endpoint except raw ticks
  • WebSocket streaming, 5 symbols
  • Released calendar actuals
  • Email support
  • 3 API keys
See plan details
Popular
Pro
$79 per month · 100,000 requests/day · 600/min
  • Everything in Starter
  • Raw tick data (/v1/ticks)
  • Priority support
  • 10 API keys
  • WebSocket streaming, 20 symbols
See plan details
Docs and implementation

Every next step is one click away.

Landing pages convert; documentation closes the loop. These are the routes a developer usually needs next.

Documentation hub

Start from the developer portal and map the API families your product needs.

Open docs

Quickstart

Make the first authenticated request and validate the setup end to end.

Read quickstart

API reference

Request and response contracts for quote, indicator, summary and calendar.

Browse reference

Integrations

How the API drops into ChatGPT, Claude, Discord, n8n, Zapier and Sheets.

See integrations
Frequently asked questions

What developers ask first.

Straight answers on limits, coverage and how the endpoint behaves in production.

Do I need any npm packages?

Not if you are on Node.js 18 or later — the native fetch() API is built in. For older Node versions, use node-fetch or axios. For TypeScript, the fetch API types are included in @types/node 18+.

How do I run concurrent requests efficiently?

Use Promise.all() to fan out multiple indicator or symbol requests simultaneously. All requests resolve in roughly the same wall-clock time as a single request — typically in roughly the same wall-clock time as a single request.

Does this work in a Next.js API route?

Yes. Use it in any Next.js API route (pages/api/ or app/api/), server component, or Server Action. For edge runtime, use the native fetch() call — no Node.js-specific packages needed.

Can I cache responses in Node.js?

Yes. Use a simple in-memory Map with timestamps, or a Redis/Upstash cache for production. The API already caches server-side — prices refresh about once a minute, indicators once per timeframe interval — so client-side caching mainly helps if you are calling at high frequency or want to reduce quota spend.

Start building

Start Building in 5 Minutes

Sign up, grab your API key, make your first request.

Every new account starts with $2.50 of pay-as-you-go credit. No card required.

Get $2.50 free credit Read the Docs