/dune/datasets

POST /api/dune/datasets

Price: 1 credit

Get a Dune dataset (table) by name: schema, columns, blockchains and description

How to use it

Get a Dune Analytics dataset (raw table) by its '{schema}.{table}' name, e.g. 'dex.trades'. Returns the table's namespace, category, description, the blockchains it covers, its full column schema (name, type, nullability and per-column description), favorite and query-reference counts, the SQL definition for curated spells, and the maintaining team. Use the column names to understand what a query over this table can select.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dataset string required — Dataset table name as '{schema}.{table}' (e.g. 'dex.trades') or a dune.com/data/{name} URL (examples: "dex.trades"; minLength: 1)

Response

• @type string (default: "DuneDataset")
• full_name string required
• namespace string nullable
• schema_name string nullable
• table_name string nullable
• table_type string nullable
• category string nullable
• category_path string nullable
• description string nullable
• blockchains array (default: [])
• is_private boolean (default: false)
• is_gated boolean (default: false)
• popular boolean (default: false)
• favorite_count integer nullable
• query_reference_count integer nullable
• table_size_bytes integer nullable
• created_at string nullable
• updated_at string nullable
• sql_definition string nullable
• maintainer object nullable
  • @type string (default: "DuneAuthor")
  • id integer nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • is_team boolean (default: false)
• columns array (default: [])
  • @type string (default: "DuneColumn")
  • name string required
  • type string nullable
  • nullable boolean nullable
  • description string nullable

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 — Dataset not found 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.