API Reference

API Endpoints

Simple, real-time APIs to capture events, detect signals, and recover revenue.

Base URL: https://api.spiderapi.com
POST/events

Capture user lifecycle events across your platform. Spider processes each event in real-time and maps it to revenue signals.

Request body
{
  "event": "kyc_approved",
  "user_id": "usr_123",
  "timestamp": "2026-03-24T10:00:00Z"
}
Response
{
  "status": "received",
  "signal_triggered": false,
  "event_id": "evt_9x2k1"
}
POST/signals

Manually trigger signal evaluation for a specific user or account. Useful for on-demand analysis.

Request body
{
  "user_id": "usr_123",
  "evaluate": ["dormant_account", "churn_risk"]
}
Response
{
  "signals": ["dormant_account"],
  "confidence": 0.91,
  "evaluated_at": "2026-03-24T10:01:00Z"
}
GET/leaks

Retrieve all detected revenue leaks across your platform, grouped by signal type.

Response
{
  "type": "dormant_account",
  "users": 42,
  "estimated_revenue_loss": 12500,
  "detected_at": "2026-03-24T08:00:00Z"
}
GET/accounts/{id}

Fetch the full signal history and revenue timeline for a specific user account.

Response
{
  "user_id": "usr_123",
  "signals": ["dormant_account"],
  "last_active": "2026-03-18T14:22:00Z",
  "balance": 12000,
  "recommended_action": "trigger_activation_flow"
}

Supported Events

Pass these as the event field in POST /events.

signup_started
kyc_approved
deposit_completed
first_trade
trade_executed
inactivity_detected

Detected Signals

Spider automatically detects these patterns from your event stream.

dormant_account

Funded but no trading activity

unfunded_account

KYC passed but no deposit

under_trading

Low frequency relative to balance

churn_risk

Engagement decay detected

Start sending events in minutes

No setup. No dashboards to configure. Real-time from the first event.