/dune/dashboards

POST /api/dune/dashboards

Price: 1 credit

Get a Dune dashboard by id or handle/slug: metadata, author, text widgets and referenced queries

How to use it

Get a Dune Analytics dashboard by its numeric id or by '{handle}/{slug}' (as in a dune.com dashboard URL). Returns the dashboard title, slug, tags, star and view counts, trending flag, created/updated timestamps, the author (analyst or team), the markdown text blocks, and the list of widgets — each naming the visualization and the underlying query (id, name, author) it renders. Use the widget query ids with the 'queries' and 'queries/results' endpoints to drill into the data.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dashboard string required — Dashboard id (numeric) or '{handle}/{slug}' or a dune.com dashboard URL (examples: "datadashboards/polymarket-overview", "190393"; minLength: 1)

Response

• @type string (default: "DuneDashboard")
• id integer required
• name string nullable
• slug string nullable
• tags array (default: [])
• is_private boolean (default: false)
• is_archived boolean (default: false)
• is_trending boolean (default: false)
• star_count integer nullable
• view_count integer nullable
• created_at string nullable
• updated_at string nullable
• author object nullable
  • @type string (default: "DuneAuthor")
  • id integer nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • is_team boolean (default: false)
• texts array (default: [])
• widgets array (default: [])
  • @type string (default: "DuneDashboardWidget")
  • visualization_id integer nullable
  • type string nullable
  • name string nullable
  • query_id integer nullable
  • query_name string nullable
  • query_author object nullable
    • @type string (default: "DuneAuthor")
    • id integer nullable
    • name string nullable
    • alias string nullable
    • image string nullable
    • is_team boolean (default: false)

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 — Dashboard 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.