Skip to main content
Feature status: pending_upstream. Hyperliquid does not currently emit question metadata on-chain. Until HL ships question records the index has nothing to populate this endpoint with. The route is wired and stable — it will start returning data automatically once HL emits it. No client changes will be needed.
HIP-4 outcomes can in principle be grouped into multi-outcome questions (e.g. “Who wins NFL MVP” with one outcome per candidate). This endpoint will surface that grouping when it exists. For now use /v1/markets to enumerate individual outcomes.

Endpoint

Response (current — feature pending)

Response (future — when HL ships questions)

/v1/questions/:qid

Returns one question’s metadata. Until HL emits questions this returns:

How to know when this goes live

Poll /v1/questions (cheap — single Postgres scan against an empty table). When count > 0, HL has shipped questions and the data is live. The feature_status and note fields will disappear from the response once data exists. For aggregating data across the outcomes belonging to one question (sum-of-probabilities, top holders across the whole event), see /v1/questions/:qid/aggregate.