/dune/queries/results

POST /api/dune/queries/results

Price: 1 credit

Get the latest cached on-chain result rows for a Dune query

How to use it

Get the latest cached result of a Dune Analytics query by its numeric id — the actual on-chain data rows the query produced on its last run. Returns the result columns (name and type), the data rows, the execution timestamp and runtime, and the total available row count. Set count to control how many rows to return. Returns not-found when the query has no cached results available.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query integer required — Query id (numeric), e.g. 5844078 or a dune.com/queries/{id} URL (examples: 5844078)
• count integer required — Number of result rows to return (min: 1)

Response

• @type string (default: "DuneQueryResult")
• query_id integer required
• execution_id string nullable
• generated_at string nullable
• runtime_seconds number nullable
• total_row_count integer nullable
• row_count integer nullable
• columns array (default: [])
  • @type string (default: "DuneResultColumn")
  • name string required
  • type string nullable
• rows array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Query not found or has no cached results Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.