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.
No credit card. $2.50 PAYG credit on sign up.
One Request. Instant Data.
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}`);Why Use TickAtlas?
Pre-Calculated, Sub-100ms
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 all symbols active on connected broker terminals.
Plug into any stack
- ChatGPT Custom GPTs
- Claude Tools
- Python / pandas
- Node.js
- Discord bots
- Slack webhooks
- n8n
- Zapier
- Google Sheets
Three Code Examples
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
Frequently Asked Questions
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 under 100ms total for a batch of 10 symbols.
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 has a 2-second server-side cache, so you only need client-side caching if you are calling at very high frequency or want to reduce costs.
Start Building in 5 Minutes
Sign up, grab your API key, make your first request.
Every new account gets $2.50 in free PAYG credits. No card required.