The Edge Your App Cannot Get From Price Data Alone.

Every request is authenticated with your API key, passed as the api_key parameter or an Authorization: Bearer header. Generate one from your account and claim 1,000 free credits.

The endpoint accepts GET and returns JSON from https://cfgi.io/api/v3/scores. Discover everything we score at https://cfgi.io/api/v3/assets (free, no key).

The newest row in each result carries latest: true plus age_seconds (seconds since that reading) and stale (true when a reading is older than its timeframe expects, for example across a market close), so you can tell a live value from a lagging one.

Crypto

Stocks

Choose what comes back with fields=. The 10 signals arrive inside components (here price means the price sub-signal); score and its classification are included in every row, along with the real asset price and market_capwhere available. Only the STOCK_MARKET index (the S&P 500) is score and price only; the crypto MARKET index returns its full components like any asset. Each requested field costs one credit per row.

Skip polling and have CFGI push each new reading to your endpoint. Add a webhook URL, token, timeframe and fields. We send a signing secret, POST the payload and retry failed deliveries. Webhook deliveries draw on the same credits as API calls: one credit per field, per reading delivered.

import crypto from 'node:crypto'
const signature = req.headers['x-cfgi-signature']
const expected = 'sha256=' + crypto
  .createHmac('sha256', YOUR_SECRET)
  .update(rawBody)
  .digest('hex')
if (signature !== expected) return res.status(401).end()

GET /api/api_request_v2.php
  ?api_key=KEY&token=BTC&period=4&fields=cfgi,whales&values=1

[
  {
    "token": "BTC",
    "nombre": "Bitcoin",
    "date": "2026-07-08 16:00:00",
    "price": 30000,
    "ultimo": true,
    "cfgi": 38,
    "data_whales": 49
  }
]

GET /api/v3/scores
  ?api_key=KEY&symbols=BTC&timeframe=1d&fields=score,whales&limit=1

{
  "data": [{
    "symbol": "BTC",
    "name": "Bitcoin",
    "asset_class": "crypto",
    "timestamp": "2026-07-08T16:00:00Z",
    "latest": true,
    "age_seconds": 900,
    "stale": false,
    "price": 30000,
    "market_cap": 594000000000,
    "score": 38,
    "classification": "Fear",
    "components": { "whales": 49 }
  }],
  "meta": { "rows": 1, "symbols": 1, "timeframe": "1d" }
}

Webhook payload: v2 to v3

If you receive score updates by webhook, this is the only change on your side. Point your handler at the v3 keys below before 1 August 2026, when your webhooks move over automatically.

POST https://your-app.com/hooks/cfgi
(no signature header)
{
  "id": 987654,
  "token": "BTC",
  "timeframe": "4h",
  "date": "2026-07-08 16:00:00",
  "price": 30000,
  "data_cfgi": 38,
  "data_search": 55,
  "data_orderbook": 41,
  "data_whales": 49
}

POST https://your-app.com/hooks/cfgi
X-CFGI-Signature: sha256=6b6f0e…
{
  "event": "score.updated",
  "token": "BTC",
  "timeframe": "4h",
  "date": "2026-07-08 16:00:00",
  "price": 30000,
  "cfgi": 38,
  "classification": "Fear",
  "data_trends": 55,
  "data_orders": 41,
  "data_whales": 49
}

• data_cfgi becomes cfgi, plus a new classification label (Fear, Greed, and so on).
• data_search becomes data_trends, and data_orderbook becomes data_orders. The other data_* signals keep their names.
• A new event field replaces the old numeric id.
• Every v3 delivery is signed: verify the X-CFGI-Signature header against your signing secret (see the Webhooks section above).

New in v3

• Stocks and the STOCK_MARKET index sit next to crypto and MARKET on the same key.
• Bearer auth: send the key as an Authorization header, not only the api_key query.
• Freshness on the live row: age_seconds and a stale flag mark a lagging reading.
• ISO 8601 UTC timestamps replace the v2 Madrid-local date strings.
• include_inactive=1 reaches delisted assets, and a free, keyless /api/v3/assets lists the whole roster.

Unchanged: the [1,99] scale, the fields × rows credit math, the history, and the X-* billing headers. Migrating is a rename, not a re-integration: keep your key, swap the endpoint and parameter names, and read score where you read cfgi.

Errors moved to a single envelope: { "error": { "code", "message" } } with the same status codes (400, 401, 402, 429). Billing headers (X-Credits-Used, X-Credits-Remaining) are identical across both versions.