Market & Pricing APIs

Acceso’s Polymarket integration exposes normalized prediction-market reads.

Use it for:

• discovery (find markets)

• monitoring (price / probability changes)

• analytics (historical series, model inputs)

It is not designed for trade execution.

API conventions

These routes are read-oriented. They are designed for analytics, monitoring, and automation.

• Auth: Authorization: Bearer $ACCESO_API_KEY

• Base URL: https://<YOUR_ACCESO_API_HOST>

• Response envelope: stable success / data / meta

Example: response envelope (shape)

{
  "success": true,
  "data": {},
  "meta": {
    "request_id": "req_1c2d3e",
    "timestamp": 1765939200
  }
}

• Normalization: timestamps are epoch seconds. IDs are opaque strings.

• Pagination (when available): limit, cursor (opaque), direction=asc|desc (route-dependent)

• Freshness: sources can be eventually consistent. “Latest” routes may be briefly cached.

Always treat cursor as opaque. Cursor semantics are endpoint-specific.

Market objects

Markets are normalized into stable, analytics-friendly objects.

What you typically get

• market_id

• title and description

• category / tags (when available)

• status (normalized lifecycle state)

• outcomes[] (each with outcome_id, label)

• created_at, open_at, close_at (when known)

• resolution_criteria (human-readable text)

Vendor-specific fields may exist. Prefer normalized fields for application logic.

Market discovery

Common operations:

• list markets (paginated)

• fetch a single market by id

• search / filter by category, status, or text

Representative routes

Route naming can vary by deployment. Typical patterns:

• GET /v1/polymarket/markets

• GET /v1/polymarket/markets/<MARKET_ID>

Common query knobs:

• q (free-text search)

• status

• category

• limit, cursor

Example: list markets (paginated)

curl -sS \
  -H "Authorization: Bearer $ACCESO_API_KEY" \
  "https://<YOUR_ACCESO_API_HOST>/v1/polymarket/markets?limit=50"

Pricing and probability

Pricing endpoints expose outcome-level prices and implied probabilities.

What you typically get

• market_id

• as_of (timestamp for the snapshot)

• outcomes[] with:

  • outcome_id

  • price (decimal)

  • probability (0–1, when exposed)

  • best_bid / best_ask (when orderbook is available)

Representative routes

Typical patterns:

• GET /v1/polymarket/markets/<MARKET_ID>/prices

• GET /v1/polymarket/markets/<MARKET_ID>/candles?interval=1m&start=<TS>&end=<TS>

“Probability” can be derived from market prices. The derivation depends on venue mechanics. Treat these values as best-effort signals, not ground truth.

Example: fetch price snapshot for a market

curl -sS \
  -H "Authorization: Bearer $ACCESO_API_KEY" \
  "https://<YOUR_ACCESO_API_HOST>/v1/polymarket/markets/<MARKET_ID>/prices"

Example: pricing response (shape)

{
  "success": true,
  "data": {
    "market_id": "mkt_123",
    "as_of": 1765939200,
    "outcomes": [
      {
        "outcome_id": "yes",
        "label": "Yes",
        "price": 0.62,
        "probability": 0.62,
        "best_bid": 0.61,
        "best_ask": 0.63
      }
    ]
  },
  "meta": {
    "request_id": "req_1c2d3e",
    "timestamp": 1765939200
  }
}

Historical series

Historical endpoints are designed for replayable analytics.

Common outputs:

• candle series (OHLCV-like)

• sampled snapshots at fixed intervals

Typical knobs:

• start, end (epoch seconds)

• interval (1m, 5m, 1h, 1d — deployment-dependent)

For stable backtests, prefer historical routes over “latest” snapshots.