Skip to main content
POST
/
v1
/
materialized-views
/
{name}
/
refresh
This refreshes a materialized view
curl --request POST \
  --url https://api.dune.com/api/v1/materialized-views/{name}/refresh \
  --header 'Content-Type: */*' \
  --header 'X-Dune-Api-Key: <x-dune-api-key>' \
  --data '{
  "performance": "<string>"
}'
{
  "execution_id": "01HZ065JVE23C23FM2HKWQP2RT",
  "sql_id": "dune.dune.result_erc_20_token_summary"
}
  • By default, the refresh runs on the medium engine. To boost performance, pass in a JSON body with {{"performance": "large"}}. Credits are consumed based on actual compute resources used for the refresh operation.
  • If you prefer medium performance, you can omit the performance parameter.
  • You must own the materialized view to refresh it.
  • After triggering the refresh, you can check the status by passing the returned execution_id into the Get Execution Status endpoint.
  • To find the name of a materialized view:

Headers

​
X-Dune-Api-Key
string
required

API Key for the service

Path Parameters

​
name
string
required

Matview Name

Query Parameters

​
api_key
string

API Key, alternative to using the HTTP header X-Dune-Api-Key

Body

*/*

MatviewsRefreshRequest

​
performance
string

Performance level of the refresh Available options: medium, large, defaults to medium

Response

OK

​
execution_id
string

Unique identifier for the execution triggered to refresh the materialized view

Example:

"01HZ065JVE23C23FM2HKWQP2RT"

​
sql_id
string

Unique identifier for the materialized view

Example:

"dune.dune.result_erc_20_token_summary"