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.
Set up a Slack Incoming Webhook, poll /v1/screener or /v1/indicator on a schedule, and forward formatted alerts to your channel of choice.
Indicator values are computed server-side on every new candle. Your app queries the result — no TA library, no candle history needed.
M1, M5, M15, M30, H1, H4, D1 — the same endpoint serves scalpers and position traders alike.
EURUSD, GBPUSD, XAUUSD, BTCUSD, USDJPY — data available for every symbol in our data.
import requests
SLACK = "https://hooks.slack.com/services/..."
data = requests.get(
"https://tickatlas.com/v1/indicator",
headers={"X-API-Key": "YOUR_API_KEY"},
params={"symbol": "XAUUSD", "indicator": "RSI_14", "timeframe": "H1"}
).json()["data"]
zone = "oversold" if data["value"] < 30 else "overbought" if data["value"] > 70 else "neutral"
requests.post(SLACK, json={"text": f"XAUUSD RSI: {data['value']:.1f} ({zone})"}) Slack Incoming Webhooks give you a URL that accepts POST requests with JSON payloads. Your script polls TickAtlas for indicator data, formats it into Slack's Block Kit structure, and POSTs to the webhook URL. Messages appear in the configured Slack channel immediately. No Slack app approval process, no OAuth — just a webhook URL. Our code examples use Slack's Block Kit for rich formatting with headers, fields, and color-coded sections.
Post a formatted multi-indicator summary for your watchlist every hour, every 4 hours, or at market open — automatically, no manual checking.
Trigger a Slack alert only when RSI goes above 70, ADX crosses 25, or MACD flips direction. Clean noise-free notifications when conditions matter.
Scan all major Forex pairs in seconds and post a single ranked message — e.g., "3 pairs approaching overbought on H4" — for your team's morning review.
Works with any Slack-compatible tool
Plug into any stack
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.
Landing pages convert; documentation closes the loop. These are the routes a developer usually needs next.
Start from the developer portal and map the API families your product needs.
Open docsMake the first authenticated request and validate the setup end to end.
Read quickstartRequest and response contracts for quote, indicator, summary and calendar.
Browse referenceHow the API drops into ChatGPT, Claude, Discord, n8n, Zapier and Sheets.
See integrationsStraight answers on limits, coverage and how the endpoint behaves in production.
No. Incoming Webhooks do not require a bot token or OAuth. You create a webhook URL from api.slack.com, and any HTTP POST to that URL will send a message to the configured channel. It is the simplest way to push messages to Slack.
Yes. The Python and Node.js examples above use Block Kit's blocks format, which supports headers, fields, sections, and dividers. You can add button elements, context blocks with timestamps, and color-coded attachments for alert severity.
Options include: a free-tier Railway.app deployment, a GitHub Actions scheduled workflow (runs every hour on cron), a $5/mo VPS with cron, or a no-code tool like Zapier with scheduled polls. The Python script runs fine on any of these.
Yes. Microsoft Teams also supports Incoming Webhooks with a similar POST-JSON pattern. The logic is identical — replace the Slack webhook URL with a Teams Incoming Webhook URL and adjust the payload format for Teams' message card structure.
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.