Materialized views store the results of a query as a table that can be queried like any other table, enabling you to build data pipelines within Dune. To learn more about how materialized views work, see the Materialized Views page.
Materialized views contribute to your storage quota. On the free tier you can only create a 1MB materialized view. Learn more at dune.com/pricing
Naming Convention
Materialized view names must follow these rules:- The full name qualifier is
dune.<your_team>.<name> - The name (last part) must be prefixed with
result_ - Example:
dune.myteam.result_daily_volume
Endpoints
Below is an overview of each endpoint for managing materialized views.| Endpoint Title | Endpoint | Description |
|---|---|---|
| Get Materialized View | GET /v1/materialized-views/{name} | Retrieves details about a specific materialized view |
| Upsert Materialized View | POST /v1/materialized-views | Creates a new materialized view or updates an existing one |
| Delete Materialized View | DELETE /v1/materialized-views/{name} | Removes a materialized view |
| List Materialized Views | GET /v1/materialized-views | Lists all materialized views for your account |
| Refresh Materialized View | POST /v1/materialized-views/{name}/refresh | Triggers a refresh to update the materialized view with latest data |
Refresh and Performance Tiers
Each refresh of a materialized view triggers a query execution and consumes credits based on the performance level:- Medium: Extended timeout, 1x compute, priority queue. Best for most queries.
- Large: Extended timeout, 2x compute, priority queue. For complex queries with joins across large tables.