API reference

Automato REST API

Premium Weekly API endpoints answer with JSON over HTTPS and reads the same data that powers the site: market regimes, trading analysis and rankings. Responses are cached for a few minutes.

Authentication

All API endpoints require an active Premium Weeklysubscription. Requests are authenticated with the session cookie you receive when you log in, so today the API is consumed from an authenticated browser session or by forwarding that cookie. Standalone API keys are not available yet.

View Premium Weekly Talk to us

Versioned endpoints (/api/v1)

The stable integration surface. All endpoints require Premium Weekly.

GET/api/v1/market/btcPremium Weekly

Same Bitcoin regime payload as /api/market/btc, under the versioned prefix.

{ "regime": [ /* market regime rows */ ] }

GET/api/v1/analysisPremium Weekly

Active analysis, newest first, with all execution levels.

{
  "analysis": [
    {
      "id": "1",
      "symbol": "SOL",
      "quoteAsset": "USDT",
      "strategy": "scalping",
      "timeframe": "fifteen_m",
      "direction": "LONG",
      "regime": "LONG_STRONG",
      "reliability": 82,
      "entryPrice": 203.42,
      "stopLoss": 198.75,
      "takeProfit1": 208.9,
      "takeProfit2": 214.3,
      "status": "active",
      "detectedAt": "2026-09-02T18:21:00.000Z"
    }
  ]
}

GET/api/v1/rankings/longPremium Weekly

The 20 most reliable active long analysis.

{ "analysis": [ /* signal objects */ ] }

GET/api/v1/rankings/shortPremium Weekly

The 20 most reliable active short analysis.

{ "analysis": [ /* signal objects */ ] }

GET/api/v1/crypto/{symbol}Premium Weekly

Up to 50 active analysis for one market. The symbol is the base asset, for example BTC or SOL.

{ "symbol": "SOL", "analysis": [ /* signal objects */ ] }

Errors

Status	Error	When it happens
401	Unauthorized	No valid session was sent with the request.
403	API access required	The account has no active Premium Weekly subscription.
400	Bad request	The request body or a parameter is invalid.

Errors are returned as { "error": "message" } with the matching HTTP status.