Explore markets

The Implyra API

A better view,
for your product.

Market discovery, wallet records and venue context. Give your users a way to see beyond the odds.

Request API access Read the docs
Built for research interfaces, data products and your next idea.REST SSE Read-only analytics

Explore the contract

Start with a question.

Choose a resource, adjust the request and take the example into your own code.

Request builder

Request windowed changes alongside current metrics. An unavailable delta is not a zero change.

Full reference
POST/markets/discover
Window
Limit
Terminal
curl --fail-with-body \  -X POST "${IMPLYRA_API_URL%/}/markets/discover" \  -H "Content-Type: application/json" \  --data-raw '{    "metrics": ["volume", "liquidity", "price"],    "deltas": [      { "metric": "volume", "window": "24h", "compare": "delta_abs" },      { "metric": "price", "window": "24h", "compare": "delta_abs" }    ],    "sort": { "metric": "volume", "window": "24h",              "compare": "delta_abs", "direction": "desc" },    "pagination": { "limit": 20 }  }'
metrics.volume
Cumulative volume in USD.
deltas.volume_24h
Read status before using the 24h change.
pagination
Continue with the returned cursor.
Example only · No request is sent from this page.

Set IMPLYRA_API_URL to your assigned REST base URL and apply the access configuration supplied during onboarding.

The available context

Build the view you need.

We confirm venue, field and historical coverage for your integration.

01

Markets

Polymarket · Kalshi · Hyperliquid

Discovery, trading activity and available price history. Keep venue identifiers, volume units and missing observations explicit.

02

Wallet research

Polymarket

Profiles, positions, closed records and P&L observations. Availability depends on the wallet, endpoint and historical window.

03

Venue comparisons

Polymarket ↔ Kalshi

Matched contracts and quoted probability differences, with confidence filters. Review settlement terms before interpreting a match.

04

Activity streams

Server-Sent Events

Subscribe to supported market, trade and wallet channels. Streaming uses a separate service and channel-specific access.

A conversation, then an integration

Tell us what
you’re building.

We’ll work through the scope before you commit to an API plan.

Discuss your integration Or explore the free dashboard
  1. 01

    The data

    Which venues, records and historical periods does your product need?

  2. 02

    The workload

    How will you query the API, and which streams would you use?

  3. 03

    The access

    Agree on scope and allocation, then receive your base URLs and access configuration.

A few details

Before you build.

Is API access included with the free dashboard?

The research dashboard is free. API access is arranged separately and quoted around your data requirements, request volume and integration support.

Do all venues offer the same analytics?

Each venue has its own endpoints and coverage. The wallet research endpoints shown here use Polymarket records; cross-venue matching covers Polymarket and Kalshi. Matches can be empty, and a returned history may be partial. We confirm the fields and periods your application needs during onboarding.

What do I need to run the examples?

Use the REST base URL and deployment access instructions supplied during onboarding. Keep credentials on your server. The request builder generates examples locally; the endpoint reference explains parameters, pagination and response fields.

How does streaming access work?

REST and SSE run on separate services. Available channels and connection access are agreed during onboarding. Some wallet streams require an authenticated session or a short-lived ticket; the streaming guide documents those requirements.