Live Tennis API · Schema

Market

CompanySportsDataReal-TimeTennis

Properties

Name Type Description
id integer
question stringnull
status stringnull
volume numbernull
liquidity numbernull
end_date stringnull
prices array Prices endpoint / match detail only; newest first
View JSON Schema on GitHub

JSON Schema

livetennisapi-com-market-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/livetennisapi-com/json-schema/livetennisapi-com-market-schema.json",
  "title": "Market",
  "x-generated": "2026-11-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/livetennisapi-com-markets-api-openapi.yml#/components/schemas/Market",
  "type": "object",
  "properties": {
    "id": {
      "type": "integer"
    },
    "question": {
      "type": [
        "string",
        "null"
      ]
    },
    "status": {
      "type": [
        "string",
        "null"
      ],
      "enum": [
        "active",
        "resolved",
        "closed",
        null
      ]
    },
    "volume": {
      "type": [
        "number",
        "null"
      ]
    },
    "liquidity": {
      "type": [
        "number",
        "null"
      ]
    },
    "end_date": {
      "type": [
        "string",
        "null"
      ],
      "format": "date-time"
    },
    "prices": {
      "type": "array",
      "description": "Prices endpoint / match detail only; newest first",
      "items": {
        "$ref": "#/$defs/Price"
      }
    }
  },
  "$defs": {
    "Price": {
      "type": "object",
      "description": "Prediction-market top-of-book quote (probability-like, [0,1]); reflects market trading, not an official line, and can lag live scores. Tagged so a synthesised quote is never mistaken for a live book.",
      "properties": {
        "side": {
          "type": [
            "integer",
            "null"
          ],
          "description": "1 = players.p1's outcome, 2 = players.p2's - decided by our name-verified match-market mapping, never by the venue's own display order (the venue lists roughly half of all pairings the other way round). Fixed 2026-09-09: ticks served before that date followed the venue's display order, so on those markets side was reversed; the mapping is stored, so re-reading any tick now returns the correct side."
        },
        "bid": {
          "type": [
            "number",
            "null"
          ]
        },
        "ask": {
          "type": [
            "number",
            "null"
          ]
        },
        "mid": {
          "type": [
            "number",
            "null"
          ],
          "description": "The venue's observed midpoint at the instant we polled or streamed it - never a model estimate. Only mid is always real; see synthetic."
        },
        "spread": {
          "type": [
            "number",
            "null"
          ]
        },
        "price_source": {
          "type": [
            "string",
            "null"
          ],
          "description": "Feed category, e.g. prediction_market"
        },
        "synthetic": {
          "type": [
            "boolean",
            "null"
          ],
          "description": "true = bid/ask are estimated from mid (mid +/- 0.005, not a live order book) - mid itself is the venue's observed midpoint, never a model estimate; false = real top-of-book from the live order-book stream; null = unknown (older ticks). The live stream attaches when a match goes live, so pre-match ticks are synthetic: true by design."
        },
        "timestamp": {
          "type": [
            "string",
            "null"
          ],
          "format": "date-time",
          "description": "When we observed this quote (UTC) - our observation clock, not a venue publication time."
        }
      }
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/livetennisapi-com-market"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.