Skip to main content
GET
/
v1
/
integrations
/
zapier
/
signal
Zapier / n8n Signal
curl --request GET \
  --url https://api.aioka.io/v1/integrations/zapier/signal \
  --header 'X-API-Key: <api-key>'
{
  "btc_price": 77882,
  "confidence": 76.8,
  "dark_pool": 65,
  "ema_200": 76196,
  "ghost_status": "WAITING",
  "id": "a1b2c3d4e5f6a7b8",
  "readable_time": "24 Apr 2026, 10:00 CEST",
  "regime": "LOW_VOLATILITY",
  "rsi": 49.5,
  "timestamp": "2026-04-24T10:00:00+02:00",
  "verdict": "ACCUMULATE"
}

​
Overview

The Zapier / n8n signal endpoint delivers a compact, flat JSON payload designed for automation platform polling. Use it to build Zaps or n8n workflows that trigger on new AIOKA verdicts — without writing any code. Tier: Basic ($49/mo) 🔒 Cache TTL: 60 seconds (server-side) Rate limit: Basic 1,000/day, 30/min. Pro 10,000/day, 100/min.

​
Response Fields

FieldTypeDescription
idstringSHA-256[:16] of ruling:ruled_at. Changes every time the verdict changes — use this as Zapier’s deduplication key
verdictstringJudiciary ruling: STRONG_BUY / BUY / ACCUMULATE / HOLD / REDUCE / SELL / STRONG_SELL / PENDING
confidencefloatJudiciary composite confidence 0–100
regimestringCurrent HMM market regime
dark_poolintDark Pool composite score 0–100
rsifloatBTC 1H RSI(14). 0 if unavailable
ema_200floatBTC 1H EMA(200). 0 if unavailable
btc_pricefloatLive BTC spot price. 0 if unavailable
ghost_statusstringGhost Trader status: WAITING or IN_POSITION
timestampstringISO 8601 datetime with Prague timezone offset, e.g. 2026-04-24T10:00:00+02:00
readable_timestringHuman-readable Prague CEST/CET time, e.g. 24 Apr 2026, 10:00 CEST

​
Zapier Quick Start

1

Get your API key

Generate a Basic-tier key at POST /v1/keys/generate or upgrade at aioka.io/pricing.
2

Create a Schedule trigger

In Zapier, create a new Zap with Schedule by Zapier → every 5 minutes.
3

Add HTTP Request action

Add an HTTP by Zapier action:
  • Method: GET
  • URL: https://api.aioka.io/v1/integrations/zapier/signal
  • Headers: X-API-Key: YOUR_KEY
4

Add a Filter for new verdicts

Add a Filter by Zapier step:
  • Only continue if id does not equal the previous id
Store the previous id in a Zapier Storage by Zapier step or use the built-in deduplication on the id field — it changes every time the verdict changes.
5

Post to Slack or Telegram

Add a final action — Slack or Telegram:
  • Message body: AIOKA Verdict: {{verdict}} ({{confidence}}% confidence) — {{readable_time}}

​
n8n Quick Start

Import the ready-made n8n workflow template:
  1. Download n8n-workflow.json
  2. Open n8n → Workflows → Import from File
  3. Set the X-API-Key credential in the HTTP Request node
  4. Activate the workflow
See the full n8n setup guide for step-by-step screenshots.

​
Example Response

{
  "id": "a1b2c3d4e5f6a7b8",
  "verdict": "ACCUMULATE",
  "confidence": 76.8,
  "regime": "LOW_VOLATILITY",
  "dark_pool": 65,
  "rsi": 49.5,
  "ema_200": 76196.0,
  "btc_price": 77882.0,
  "ghost_status": "WAITING",
  "timestamp": "2026-04-24T10:00:00+02:00",
  "readable_time": "24 Apr 2026, 10:00 CEST"
}

​
Deduplication Strategy

The id field is a SHA-256[:16] fingerprint of f"{ruling}:{ruled_at}". It is stable across the 60-second cache window and changes the instant a new verdict is issued. Zapier: Set up a Filter action that compares id to the previous stored value. Only continue when they differ. n8n: Use the built-in IF node with ={{$json.id}} !== {{$node["Set"].json.lastId}}.

​
Error Responses

StatusErrorCause
401missing_api_keyNo X-API-Key header
401invalid_api_keyKey not found or inactive
403tier_requiredFree tier key — Basic or higher required
429daily_limit_exceededDaily quota exhausted
429rate_limit_exceededPer-minute burst exceeded

Authorizations

​
X-API-Key
string
header
required

Your AIOKA Intelligence API key (format: aik_{tier}_{random})

Response

Latest AIOKA signal bundle for automation workflows.

Signal payload for Zapier and n8n automation workflows.

Key differences from the Pine Script endpoint (Sprint 229):

  • id — SHA-256 fingerprint of verdict+timestamp; changes on every new ruling, enabling Zapier deduplication.
  • timestamp — ISO 8601 with Prague TZ offset (e.g. +02:00) rather than Unix epoch, so Zapier can display the time directly.
  • readable_time — Human-readable Prague CEST/CET string for Telegram / Slack message bodies, e.g. "24 Apr 2026, 10:00 CEST".
​
id
string
required

SHA-256[:16] fingerprint of ruling+ruled_at. Changes each time the verdict changes — use this as Zapier's deduplication key.

​
verdict
string
required

Judiciary ruling (STRONG_BUY / BUY / ACCUMULATE / HOLD / REDUCE / SELL / STRONG_SELL / PENDING).

​
confidence
number
required

Judiciary composite confidence 0-100.

​
regime
string
required

Current market regime (BULL_TRENDING / HIGH_VOLATILITY / LOW_VOLATILITY / ...).

​
dark_pool
integer
required

Dark Pool composite score 0-100.

​
rsi
number
required

BTC 1H RSI(14). 0 if unavailable.

​
ema_200
number
required

BTC 1H EMA(200). 0 if unavailable.

​
btc_price
number
required

Live BTC spot price. 0 if unavailable.

​
ghost_status
string
required

Ghost Trader status (WAITING / IN_POSITION).

​
timestamp
string
required

ISO 8601 datetime with Prague timezone offset, e.g. '2026-04-24T10:00:00+02:00'.

​
readable_time
string
required

Human-readable Prague CEST/CET time, e.g. '24 Apr 2026, 10:00 CEST'.