Stream live and historical trade ideas.

The Trade Ideas API is a JSON REST surface with five read endpoints:

• GET /v1/trade-ideas/active — every trade idea with status LIVE, newest published_at first.
• GET /v1/trade-ideas/closed — recently terminal ideas (TP2_HIT, SL_HIT, EXPIRED, WITHDRAWN) within the lookback window.
• GET /v1/trade-ideas/history — full published archive (LIVE plus terminal rows), paginated.
• GET /v1/trade-ideas/reports — aggregate performance metrics (win rate, ROI, hit counts) for a day / week / month / year or custom IST date window.
• GET /v1/trade-ideas/{id} — one idea by id; a successful response is the trade idea JSON object at the root, not an envelope with data.

LIVE rows may still track without an entry stamp: use entry_hit_at, status, and hit timestamps in the JSON—not informal labels—to decide how you surface them in your own systems (Status values).

All evaluation against the exchange uses Bybit USDⓈ perpetual ticker last traded price (lastPrice, abbreviated LTP), not index or mark prices. Hits on entry, TP, and SL are derived from those prices on the tracker.

All responses are JSON; timestamps are ISO 8601 UTC instants on the wire (trailing Z). Numeric prices and percentages are strings so clients preserve precision without float parsing.

Access is layered: a per-partner bearer token (provided when your integration is onboarded), optional per-client IP allowlists, and always-on rate limits. Bearer tokens are required in production.

Bearer token (required)

Send your assigned token on every request:

Authorization: Bearer tia_live_…

Store the token as a secret environment variable (for example TIA_API_TOKEN on Railway) and attach it to your HTTP client — no URL or response-format changes are required.

export TIA_API_TOKEN="tia_live_…"
curl -sS -H "Authorization: Bearer $TIA_API_TOKEN" "https://project-tia.app/v1/trade-ideas/active"

Per-client IP allowlists

When IP allowlisting is required for your integration, requests that include your bearer token must originate from an IP or CIDR registered for your account. Multiple partners may share the same egress IP (for example Railway) and remain distinguishable because each has a unique token.

Deprecated (do not use)

• Global IP-only allowlists — superseded by per-client IP lists used together with bearer tokens.
• TIA_PUBLIC_API_BEARER_TOKEN environment variable — ignored; use the per-partner token provided at onboarding instead.
• /v1/picks/* paths — redirect to /v1/trade-ideas/* with HTTP 308; migrate callers to the new paths.
• API keys, scopes, and self-service token registration — not supported on this API.

Default quota: 120 requests per minute with a burst of 60. When you send a valid bearer token, limits apply per integration (not only per IP).

Prefer long polling on /v1/trade-ideas/active (see below)—one hanging request per update cycle uses fewer hits than spraying sub-second polls. Short interval polling remains fine under the quota.

When you exceed the limit you will receive an HTTP 429 with a Retry-After header (in seconds):

{
  "error": "rate_limited"
}

Every visible trade idea has exactly one wire status:

For some ideas classified at publish time, take-profit / stop-loss / milestones are tracked by the tracker only after entry_hit_at becomes non-null. Until then,LIVE persists and later hit timestamps stay null even though price moves in the broader market.

expiry_at is the published validity cut-off. Operators may shorten it on a LIVE idea (dashboard early expire); integrators should accept an extra trade_idea.updated with a smaller expiry_at while the idea remains LIVE. If TP2 or SL triggers before then, status becomes terminal; otherwise EXPIRED. A touch of tp1_price records tp1_hit_at without changing status; the trade idea can remain LIVE.

For in-app widgets and partner overlays, map potential profit to est_potential_pct (leverage-adjusted move to TP2 at publish time). Two additive fields support deeplink and coin imagery:

• mudrex_deeplink — opens Mudrex futures with published entry, SL, and TP1. Null without a Mudrex asset id.
• logo_url — verified images.mudrex.com URL or a manual override. Null until probed OK or overridden.

Optional fields for in-app deeplinks and coin imagery. Both may be null until catalogue data is available — safe to ignore if your integration does not use them.

Every trade idea object exposes the fields below with this key order on the wire. Numeric prices and percentages are strings so callers can parse with decimal libraries without floats.

{
  "id": "8c2a9b7e-4f12-4d8a-9e3b-7a6e5b1c2d3f",
  "symbol": "BTCUSDT",
  "direction": "LONG",
  "margin_type": "ISOLATED",
  "leverage": 10,
  "entry_price": "62500.00000000",
  "tp1_price": "63500.00000000",
  "tp2_price": "64500.00000000",
  "stop_loss": "62000.00000000",
  "est_potential_pct": "1.60",
  "est_loss_pct": "0.80",
  "risk_reward_ratio": "1:2",
  "confidence": "HIGH",
  "status": "LIVE",
  "published_at": "2026-05-12T13:42:01.000Z",
  "expiry_at": "2026-05-13T13:42:01.000Z",
  "entry_hit_at": null,
  "tp1_hit_at": null,
  "tp2_hit_at": null,
  "sl_hit_at": null,
  "expired_at": null,
  "withdrawn_at": null,
  "resolved_at": null,
  "mudrex_deeplink": "mudrex://futures-buy-sell/abc123/long/BTCUSDT/10/62500.00000000/62000.00000000/63500.00000000",
  "logo_url": "https://images.mudrex.com/BTC.png"
}

Withdrawn trades use the same field order; terminal example WITHDRAWN:

{
  "id": "9d3bacc1-aaaa-bbbb-cccc-dddddddddddd",
  "symbol": "ETHUSDT",
  "direction": "SHORT",
  "margin_type": "ISOLATED",
  "leverage": 5,
  "entry_price": "3000.00000000",
  "tp1_price": "2900.00000000",
  "tp2_price": "2850.00000000",
  "stop_loss": "3050.00000000",
  "est_potential_pct": "2.40",
  "est_loss_pct": "0.80",
  "risk_reward_ratio": "1:3",
  "confidence": "HIGH",
  "status": "WITHDRAWN",
  "published_at": "2026-05-14T09:00:00.000Z",
  "expiry_at": "2026-05-15T09:00:00.000Z",
  "entry_hit_at": null,
  "tp1_hit_at": null,
  "tp2_hit_at": null,
  "sl_hit_at": null,
  "expired_at": null,
  "withdrawn_at": "2026-05-14T09:42:03.000Z",
  "resolved_at": "2026-05-14T09:42:03.000Z",
  "mudrex_deeplink": "mudrex://futures-buy-sell/def456/short/ETHUSDT/5/3000.00000000/3050.00000000/2850.00000000",
  "logo_url": "https://images.mudrex.com/ETH.png"
}

Integrations may receive signed HTTPS POST payloads on URLs provisioned for your environment—an alternative to polling /v1/trade-ideas/active. Delivery starts when a trade idea is published (LIVE), continues on materially relevant live updates (entry / TP1 progress, terminals), and uses the same snake_case trade_idea object as REST. Limit orders waiting for a fill show LIVE with entry_hit_at: null exactly like REST.

• Headers include Content-Type: application/json, X-TIA-Timestamp (Unix milliseconds), and X-TIA-Signature: sha256=<hex digest> where digest is HMAC-SHA256 over {timestamp}.{rawBody} (ASCII dot between the two). Optional X-TIA-Webhook-Event-Group-Id matches envelope event_id; X-TIA-Webhook-Event-Type mirrors envelope event_type.
• Lifecycle events: trade_idea.published (first publish), trade_idea.updated (entry or TP1 progress, or validity shortened while LIVE), trade_idea.closed (TP2, SL, expiry, or withdrawal). Connectivity checks may send integration.ping.

{
  "schema_version": 1,
  "event_id": "8c2a9b7e-4f12-4d8a-9e3b-7a6e5b1c2d3f",
  "event_type": "trade_idea.published",
  "occurred_at": "2026-05-12T13:42:01.000Z",
  "trade_idea":   {
    "id": "8c2a9b7e-4f12-4d8a-9e3b-7a6e5b1c2d3f",
    "symbol": "BTCUSDT",
    "direction": "LONG",
    "margin_type": "ISOLATED",
    "leverage": 10,
    "entry_price": "62500.00000000",
    "tp1_price": "63500.00000000",
    "tp2_price": "64500.00000000",
    "stop_loss": "62000.00000000",
    "est_potential_pct": "1.60",
    "est_loss_pct": "0.80",
    "risk_reward_ratio": "1:2",
    "confidence": "HIGH",
    "status": "LIVE",
    "published_at": "2026-05-12T13:42:01.000Z",
    "expiry_at": "2026-05-13T13:42:01.000Z",
    "entry_hit_at": null,
    "tp1_hit_at": null,
    "tp2_hit_at": null,
    "sl_hit_at": null,
    "expired_at": null,
    "withdrawn_at": null,
    "resolved_at": null,
    "mudrex_deeplink": "mudrex://futures-buy-sell/abc123/long/BTCUSDT/10/62500.00000000/62000.00000000/63500.00000000",
    "logo_url": "https://images.mudrex.com/BTC.png"
  }
}

Verify timestamps within a reasonable clock skew window; tolerate at-least-once deliveries by deduplicating on event_id.

{
  "schema_version": 1,
  "event_id": "9f2c…",
  "event_type": "integration.ping",
  "occurred_at": "2026-05-12T13:43:01.000Z",
  "message": "Handshake test from Project TIA."
}

Errors return JSON with at least an error code. Validation responses from route handlers usually include message with a plain-language hint; clients should not depend on the exact copy of message.

Breaking changes are called out explicitly. Integration requirements are in Access.