> ## Documentation Index > Fetch the complete documentation index at: https://coinstats.app/docs/llms.txt > Use this file to discover all available pages before exploring further. # Event Cross Venue > Matched markets on the other venue (Kalshi <-> Polymarket) **3** credits per request
* For each child market of the event, the best-matching market on the *other* venue, with a `confidence` score (0..1) and price `delta`. * `meta.curated` / `meta.matched` tell you how many child markets were eligible and how many found a counterpart. * Use it to compare an entire race or series across both books in one call. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/prediction/events/{slug}/cross-venue openapi: 3.0.0 info: title: CoinStats Public API description: >- CoinStats Public API — programmatic access to market data, news, NFTs, wallets, exchange connections, and user portfolios. Authenticate every request with the `X-API-KEY` header (or an OAuth Bearer token in the `Authorization` header). Generate keys at https://openapi.coinstats.app. version: '1.0' contact: {} servers: - url: https://api.coinstats.app security: [] tags: - name: CoinStats description: '' - name: Market Data description: >- The Market Data section of the API provides endpoints to access a wide range of market-related information, including cryptocurrency coins, ticker data, and fiat currency rates. This category offers comprehensive data to help users monitor and analyze the cryptocurrency market, track prices, and gain insights into market trends - name: News description: >- The News section of the API allows you to access news articles and updates related to cryptocurrencies and the blockchain industry. It provides valuable information from various sources to keep you informed about the latest developments - name: NFTs description: >- The NFT section of the API provides endpoints to interact with Non-Fungible Tokens (NFTs), which are unique digital assets stored on a blockchain. These endpoints allow you to retrieve information about NFTs, including collections, assets, trending NFTs, and specific assets associated with wallet addresses. - name: Wallet Data description: >- The Wallet section of the API provides a comprehensive set of endpoints to manage and interact with wallets. It enables users to retrieve wallet balances, monitor syncing status, fetch transaction data, and synchronize wallet information with the blockchain. By integrating these endpoints into your application, you can offer robust wallet functionality to your users. - name: Exchange Connection description: >- The Exchange Connection section of the API provides a comprehensive set of endpoints to manage and interact with exchanges. It enables users to retrieve exchange balances, monitor syncing status, fetch transaction data. By integrating these endpoints into your application, you can offer robust exchange portfolio tracking functionality to your users. - name: User Portfolio description: >- The Portfolio section of the API provides a comprehensive set of endpoints to manage and interact with Share Portfolios. It enables users to retrieve current Portfolio Coins and Transactions. - name: Usage description: The Usage section provides account-level API usage data. - name: Status description: The Status section provides API availability checks. - name: Prediction · Markets description: >- Polymarket markets: list/trend/detail, live CLOB prices and order book, OHLC candles, and price history. Prices are probabilities in 0..1, money is USD, dates are ISO 8601. - name: Prediction · Events description: >- Polymarket events — groups of related markets (e.g. one market per candidate). List, trend, and fetch an event with its child markets. - name: Prediction · Traders description: >- Trader leaderboard plus deep per-trader analytics: profile, open positions, trade history, daily PnL, category stats, aggregate trade stats, and composite score. - name: Prediction · Analytics description: >- Platform-wide analytics: overview stats, smart-money and whale traders, trending-by-smart-money markets, and composite market signals. - name: Prediction · Search description: Full-text search across Polymarket events, markets, and traders. paths: /v1/prediction/events/{slug}/cross-venue: get: tags: - Prediction · Events summary: Matched markets on the other venue (Kalshi <-> Polymarket) operationId: event-cross-venue parameters: - name: slug required: true in: path schema: type: string responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/EventCrossVenueResponseDto' '400': description: Bad Request content: application/json: example: statusCode: 400 message: Bad Request requestId: 11111111-2222-3333-4444-555555555555 path: '401': description: Unauthorized content: application/json: example: statusCode: 401 message: Unauthorized requestId: 11111111-2222-3333-4444-555555555555 path: '403': description: Forbidden content: application/json: example: statusCode: 403 message: Forbidden requestId: 11111111-2222-3333-4444-555555555555 path: '404': description: Not Found content: application/json: example: statusCode: 404 message: Not Found requestId: 11111111-2222-3333-4444-555555555555 path: '409': description: Conflict (for some endpoints) content: application/json: example: statusCode: 409 message: Transactions not synced requestId: 11111111-2222-3333-4444-555555555555 path: '429': description: Too Many Requests content: application/json: example: statusCode: 429 message: Rate limit exceeded requestId: 11111111-2222-3333-4444-555555555555 path: '503': description: Service Unavailable content: application/json: example: statusCode: 503 message: Service Unavailable. Please Contact Support security: - X-API-KEY: [] x-codeSamples: - lang: curl label: cURL source: |- curl --request GET \ --url 'https://api.coinstats.app/v1/prediction/events//cross-venue' \ --header 'X-API-KEY: ' - lang: python label: Python source: >- import requests url = "https://api.coinstats.app/v1/prediction/events//cross-venue" headers = {"X-API-KEY": ""} response = requests.request("GET", url, headers=headers) print(response.json()) - lang: javascript label: JavaScript source: >- const options = {method: 'GET', headers: {'X-API-KEY': ''}}; fetch('https://api.coinstats.app/v1/prediction/events//cross-venue', options) .then((response) => response.json()) .then((response) => console.log(response)) .catch((err) => console.error(err)); - lang: php label: PHP source: |- "https://api.coinstats.app/v1/prediction/events//cross-venue", CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "GET", CURLOPT_HTTPHEADER => [ "X-API-KEY: " ], ]); $response = curl_exec($curl); $err = curl_error($curl); curl_close($curl); if ($err) { echo "cURL Error #:" . $err; } else { echo $response; } - lang: go label: Go source: "package main\n\nimport (\n\t\"fmt\"\n\t\"io\"\n\t\"net/http\"\n)\n\nfunc main() {\n\n\turl := \"https://api.coinstats.app/v1/prediction/events//cross-venue\"\n\n\treq, _ := http.NewRequest(\"GET\", url, nil)\n\n\treq.Header.Add(\"X-API-KEY\", \"\")\n\n\tres, _ := http.DefaultClient.Do(req)\n\n\tdefer res.Body.Close()\n\tbody, _ := io.ReadAll(res.Body)\n\n\tfmt.Println(string(body))\n}" - lang: java label: Java source: >- HttpResponse response = Unirest.get("https://api.coinstats.app/v1/prediction/events//cross-venue") .header("X-API-KEY", "") .asString(); components: schemas: EventCrossVenueResponseDto: type: object properties: success: type: boolean description: Whether the request succeeded example: true timestamp: type: string description: ISO 8601 timestamp the response was generated example: '2025-06-19T12:00:00.000Z' meta: $ref: '#/components/schemas/EventCrossVenueMetaDto' data: $ref: '#/components/schemas/EventCrossVenueDataDto' required: - success - timestamp - data EventCrossVenueMetaDto: type: object properties: curated: type: number description: Child markets in curated groups matched: type: number description: Child markets with a counterpart EventCrossVenueDataDto: type: object properties: source: type: string enum: - polymarket - kalshi description: The *other* venue that was searched for counterparts example: kalshi childMarkets: type: number description: Number of child markets in the event matches: description: One entry per child market with a confident counterpart type: array items: $ref: '#/components/schemas/EventCrossVenueMatchItemDto' EventCrossVenueMatchItemDto: type: object properties: marketSlug: type: string description: Child market slug on the requested venue question: type: string groupId: type: string description: Curated cross-venue group id currentYes: type: number description: Current Yes price of the child market match: $ref: '#/components/schemas/CrossVenueMarketMatchDto' CrossVenueMarketMatchDto: type: object properties: source: type: string enum: - polymarket - kalshi description: Venue the matched market lives on example: kalshi ticker: type: string description: Venue-native identifier (Kalshi ticker / Polymarket slug) example: KXBRPRES-26-LULA question: type: string yesPrice: type: number description: Current Yes price on the matched venue endDate: type: string format: date-time volume24hr: type: number confidence: type: number description: Match similarity 0..1 example: 0.96 method: type: string description: How the match was produced example: embedding delta: type: number description: currentYes minus the matched venue's yesPrice example: -0.015 groupId: type: string description: Curated cross-venue group id url: type: string description: Relative URL of the group externalUrl: type: string description: Link to the market on the other venue securitySchemes: X-API-KEY: type: apiKey in: header name: X-API-KEY description: >- API key required to access the endpoints. Generate one from your dashboard at https://openapi.coinstats.app and pass it in the `X-API-KEY` request header. Never expose your key in client-side code. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.