POST /api/dune/datasets/search
Price: 1 credit
Search the Dune dataset catalog by keyword, blockchain or category
Search the Dune Analytics dataset (table) catalog. Provide q to match dataset names, chain to filter to a single blockchain, and/or category to filter by data-type code. Returns each matching dataset's name, namespace, category, covered blockchains, description and favorite/query-reference counts. Use a returned name with the 'datasets' endpoint for the full schema.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)q string nullable — Keyword to search dataset names bychain string nullable — Filter to a single blockchain by name (e.g. 'ethereum'); see the blockchains endpointcategory string nullable — Filter by dataset source category (one of: "decoded", "spell", "curated", "abstraction", "community")count integer required — Number of datasets to return (min: 1)@type string (default: "DuneDataset")full_name string requirednamespace string nullableschema_name string nullabletable_name string nullabletable_type string nullablecategory string nullablecategory_path string nullabledescription string nullableblockchains array (default: [])is_private boolean (default: false)is_gated boolean (default: false)popular boolean (default: false)favorite_count integer nullablequery_reference_count integer nullabletable_size_bytes integer nullablecreated_at string nullableupdated_at string nullablesql_definition string nullablemaintainer object nullable@type string (default: "DuneAuthor")id integer nullablename string nullablealias string nullableimage string nullableis_team boolean (default: false)columns array (default: [])@type string (default: "DuneColumn")name string requiredtype string nullablenullable boolean nullabledescription string nullable422 — 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 — The entity was not found, or a precondition failed 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.