Signal Providers

​

Overview

​

How to get access

1. Ask your contact at Innova for a provider token and the x-community-slug of your community (for example my-community).
2. Keep both private. Never paste them in chats, emails or repositories.
3. Start with the sandbox endpoint (/signals/test) before sending anything real.

​

Endpoints

​

Authentication

Authorization: Bearer <YOUR_TOKEN>
x-community-slug: <YOUR_COMMUNITY>
Content-Type: application/json

• This is not a free-form API key. The token is personal and is handed to you by Innova (see “How to get access”). The x-community-slug header is mandatory on every call.
• The token is personal: whoever has it can send signals in your name, so do not share it and never paste it in chats or emails.
• No token, or a revoked token: HTTP 401.
• Your signals are isolated inside your community.

​

The JSON you send

{
  "signal_id": "my-strategy-EURUSD-15m-20261011T1430Z",
  "symbol": "EURUSD",
  "direction": "buy",
  "entry": 1.10000,
  "generated_at": "2026-10-11T14:30:05.120Z",
  "sl": 1.09500,
  "tps": [1.10500, 1.11000, 1.11500],
  "lots": 0.10,
  "risk_percent": 1.0,
  "strategy": "my-strategy",
  "comment": "confirmed cross on M15",
  "timeframe": 15
}

​

Idempotency

• If you retry because of a network failure, send the same signal_id (and the same body).
• The second call returns "status": "duplicate" with the first result and no extra trade is opened.
• Never reuse a signal_id for a different signal: the second one would be discarded as a repeat.
• We also answer duplicate with code active_same_direction if you already have an open signal on the same symbol and direction. We do not stack positions.

​

Freshness

​

Rejection codes

​

The response

{
  "accepted": true,
  "status": "published",
  "code": "ok",
  "detail": "Señal aceptada y publicada al motor de copia.",
  "signal_id": "my-strategy-EURUSD-15m-20261011T1430Z",
  "signal_source": "provider:aaaaaaaa:my-strategy",
  "symbol": "EURUSD",
  "direction": "buy",
  "generated_at": "2026-10-11T14:30:05.120000+00:00",
  "received_at": "2026-10-11T14:30:05.480000+00:00",
  "published": true,
  "dry_run": false,
  "freshness": { "accepted": true, "code": "fresh", "age_seconds": 0.36 }
}

• status: published (copied), simulated (sandbox), duplicate or rejected.
• published is true only if the signal reached the copy engine. If it is false, read code.
• signal_source is the identifier accounts use to subscribe to your strategy. Send it to your community owner.
• received_at - generated_at is your delivery latency. Log it.

​

Sandbox

​

Examples

import requests
from datetime import datetime, timezone

BASE = "https://cloud.innova-trading.com"
headers = {
    "Authorization": "Bearer <YOUR_TOKEN>",
    "x-community-slug": "<YOUR_COMMUNITY>",
}
now = datetime.now(timezone.utc)
signal = {
    "signal_id": "my-strategy-EURUSD-15m-20261011T1430Z",  # same id on every retry
    "symbol": "EURUSD",
    "direction": "buy",
    "entry": 1.10000,
    "generated_at": now.strftime("%Y-%m-%dT%H:%M:%S.") + f"{now.microsecond // 1000:03d}Z",
    "sl": 1.09500,
    "tps": [1.10500, 1.11000],
    "strategy": "my-strategy",
    "timeframe": 15,
}

# Sandbox first: /signals/test publishes nothing
resp = requests.post(f"{BASE}/api/v1/provider/signals/test", json=signal,
                     headers=headers, timeout=10)
body = resp.json()
print(resp.status_code, body["status"], body["code"])

curl -X POST "https://cloud.innova-trading.com/api/v1/provider/signals/test" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "x-community-slug: <YOUR_COMMUNITY>" \
  -H "Content-Type: application/json" \
  -d '{
    "signal_id": "my-strategy-EURUSD-15m-20261011T1430Z",
    "symbol": "EURUSD",
    "direction": "buy",
    "entry": 1.10000,
    "generated_at": "2026-10-11T14:30:05Z",
    "sl": 1.09500,
    "tps": [1.10500, 1.11000],
    "strategy": "my-strategy"
  }'

curl "https://cloud.innova-trading.com/api/v1/provider/signals/decisions?limit=20" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "x-community-slug: <YOUR_COMMUNITY>"

​

Integration checklist

1. Ask your contact at Innova for the token and the x-community-slug.
2. Send a signal to /signals/test. Expect "status": "simulated".
3. Trigger a rejection on purpose (send a generated_at from one hour ago) and confirm your code handles code: "stale".
4. Send an invented field and confirm your code handles the 422.
5. Check that your code retries with the same signal_id when a call fails (the Python kit, when available, does it for you). The sandbox always answers simulated: duplicate only shows up on the real /signals, so you will see it there for the first time. That is expected.
6. Only then switch to /signals.
7. Send us the signal_source from the response so we can subscribe accounts.

​

Convert your PineScript indicator

1. Paste the prompt and your Pine code into your assistant, and save the result as strategy.py.
2. Export your candles and your indicator’s signals from TradingView to two CSV files. The Strategy Tester trade list shows the time of the candle after the signal: in that case add --expected-shift 1 to the command in step 3.
3. Run innova-provider parity --bars bars.csv --expected expected.csv --symbol EURUSD --timeframe 15 --strategy-name my-strategy.
4. Acceptance criterion: 99 % of the signals match. --warmup defaults to your REQUIRED_BARS (live, evaluate always starts with that full history): you do not need to pass it. Check convergence: run the tool with two values of REQUIRED_BARS (for example 300 and 600) and keep the larger one if the result improves; the tool also prints an AVISO: when more history raises the match. Indicators with path-dependent state (supertrend, ATR/RMA/EMA, trailing stops) do not converge with “5 times the period”: measured with a supertrend + RSI, REQUIRED_BARS = 70 gave 94 % and 150 gave 100 %; start at 300. The tool answers NO APROBADO: historia insuficiente (even at 100 %) when the CSV has fewer than 4 times REQUIRED_BARS candles (the message gives the exact figure) or when fewer than 10 signals are compared. Your CSV must meet both conditions: at least 4 times REQUIRED_BARS candles AND at least 10 Pine signals in that stretch; if your Pine gives fewer, export more history until it does (on M15 with little activity that can take months); Pine signals before the first evaluated candle are ignored and only reported. If it still falls short, the tool lists every difference. Paste them back to your assistant and ask it to fix the conversion.
5. Only then move on to the sandbox (/signals/test) and, last, to /signals.

​

Ready-made Python kit

​

Installation

​

Flow

innova-provider init my-strategy      # creates the folder: strategy.py, config.env, README.md
cd my-strategy
# 1. fill in config.env (token and slug: we give them to you)
# 2. replace evaluate() in strategy.py with your logic
innova-provider parity --bars bars.csv --expected expected.csv \
    --symbol EURUSD --timeframe 15 --strategy-name my-strategy   # 99 % or more
innova-provider history --bars-csv bars.csv ...   # optional: your past signals (backtest-marked)
innova-provider run --dry-run --once  # sandbox: publishes nothing
innova-provider run                   # real

​

If the network fails

• The client makes up to 4 attempts per send (the first plus 3 retries). If it still does not arrive, the log says SEÑAL PERDIDA with the candle time and the signal_id.
• If the cause was the network or a 5xx, the runner retries it once in the next cycle with the same signal_id (the server does not duplicate), only while the candle is still within the 120 s freshness window (true on M1, not on longer candles; the log says so). A 401 or 422 is not retried.
• After a long outage the log says Se omitieron N velas sin evaluar (desde X hasta Y): the runner only evaluates the last closed candle, so signals of those candles are not sent and not replayed (they would arrive stale). A restart between a candle close and the next cycle also loses that candle.
• In --dry-run the 120 s candle-age guard is not applied: a test with the market closed passes and the same candle would be skipped in real mode. The reported generated_at->received_at latency includes the client retries.

​

Your past signals (history)

innova-provider history --bars-csv bars.csv --symbol EURUSD --timeframe 15 \
    --strategy-name my-strategy               # your last 50 past signals, from your own candles
innova-provider history --last 100            # candles downloaded from /api/external/bars

​

History limits

​

Prefer another language?

• Endpoints (see “Endpoints” above): read candles from /api/external/bars, send signals to /api/v1/provider/signals/test (sandbox) and then /api/v1/provider/signals.
• Headers: Authorization: Bearer <token> and x-community-slug.
• Fields: exactly those in “The JSON you send”; an unknown field is a 422.
• Stop and targets: check on your side that sl and tps are on the right side of entry; the server does not check it.
• signal_id: deterministic (strategy + symbol + timeframe + candle time), and retry with the same one. See “Idempotency”.
• 120 s guard: generate the signal when the candle closes and only send it if that close was at most 120 s ago. generated_at is “now” and the server rejects it as stale past 120 s (see “Freshness”). Do not send the signal of an old candle (weekend, delayed data).
• Candles: use only closed ones; drop the one still forming.

​

Next Steps