Update saved query

PATCH

data

lake

queries

{query_id}

curl -X PATCH 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Applied volume by currency (30d)",
    "range_mode": "rolling",
    "rolling_days": 30
  }'

{
  "data": {
    "id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "instance_id": "instance_073f7ffe-9dfd-42ce-aa50-d1dca1788adc",
    "owner_user_id": "user_01K4EX0BRXHNNGCRVT2TPNK07W",
    "name": "Applied volume by currency (30d)",
    "description": "APPLIED transaction counts by currency",
    "sql": "SELECT currency, COUNT(*) AS txn_count FROM transactions GROUP BY currency LIMIT 1000",
    "range_mode": "rolling",
    "rolling_days": 30,
    "created_at": "2026-08-12T09:28:16.864765Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "FORBIDDEN",
    "message": "lake query mutation is not permitted"
  }
}

Update a saved lake query. Send only the fields you want to change. Changing the SQL or date range does not rewrite past query runs. Those runs keep the snapshot from when they executed. Only the query owner or an admin can update it. If you change range_mode to fixed, send start_date and end_date. If you change it to rolling, send rolling_days.

Authorization

Blnk Cloud APIs support any one of the following authentication methods. All of them work with your CLOUD_API_KEY or OAUTH_ACCESS_TOKEN.

Bearer token
X-Blnk-Key header
X-API-Key header

Pass Authorization: Bearer CLOUD_API_KEY or Authorization: Bearer OAUTH_ACCESS_TOKEN.

string

required

Cloud API key or OAuth access token. Create credentials in API keys or OAuth.

Pass X-Blnk-Key: CLOUD_API_KEY or X-Blnk-Key: OAUTH_ACCESS_TOKEN.

string

required

Cloud API key or OAuth access token. Create credentials in API keys or OAuth.

Pass X-API-Key: CLOUD_API_KEY or X-API-Key: OAUTH_ACCESS_TOKEN.

string

required

Cloud API key or OAuth access token. Create credentials in API keys or OAuth.

Path

curl -X PATCH 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Applied volume by currency (30d)",
    "range_mode": "rolling",
    "rolling_days": 30
  }'

string

required

Unique id of the saved query (lake_query_...). Get it from List saved queries or Get saved query.

Body

string

Unique id of the instance (instance_...). Get it from get instance details. Do not pass deployment_id. Send this to move the query to a different instance in the same workspace.

string

Replacement label shown in Insights and copied onto later query runs. Maximum 160 characters.

string

Replacement note about what the query returns. Maximum 1000 characters.

string

Replacement read-only DuckDB SELECT or WITH. Same table and statement rules as Create new query. Later runs use this SQL. Past runs keep the old snapshot.

string

How Cloud should pick the lake date range on later runs. fixed uses start_date and end_date. rolling uses the last rolling_days days, resolved at run time.

string

First day of lake history. Required when you set range_mode to fixed. ISO date or datetime.

string

Last day of lake history. Required when you set range_mode to fixed. Must be after start_date.

integer

Number of days of lake history Cloud opens on later runs (1 to 3650). Required when you set range_mode to rolling. Cloud resolves the window at run time.

Response

{
  "data": {
    "id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "instance_id": "instance_073f7ffe-9dfd-42ce-aa50-d1dca1788adc",
    "owner_user_id": "user_01K4EX0BRXHNNGCRVT2TPNK07W",
    "name": "Applied volume by currency (30d)",
    "description": "APPLIED transaction counts by currency",
    "sql": "SELECT currency, COUNT(*) AS txn_count FROM transactions GROUP BY currency LIMIT 1000",
    "range_mode": "rolling",
    "rolling_days": 30,
    "created_at": "2026-08-12T09:28:16.864765Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "FORBIDDEN",
    "message": "lake query mutation is not permitted"
  }
}

string

Unique id of this saved query (lake_query_...).

string

Unique id of the instance (instance_...) this query is bound to after the update.

string

User who created the query. The owner does not change when you update other fields.

string

Current label after the update.

string

Current note after the update.

string

Current SELECT or WITH after the update. Later runs use this SQL.

string

How Cloud picks the lake date range on later runs: fixed or rolling.

timestamp

First day of lake history for a fixed query. Omitted when range_mode is rolling.

timestamp

Last day of lake history for a fixed query. Omitted when range_mode is rolling.

integer

Number of days of lake history to open when range_mode is rolling. 0 when the query is fixed.

timestamp

When the saved query was first created. This does not change on update.

timestamp

When this update was applied.

Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.

curl -X PATCH 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Applied volume by currency (30d)",
    "range_mode": "rolling",
    "rolling_days": 30
  }'

{
  "data": {
    "id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "instance_id": "instance_073f7ffe-9dfd-42ce-aa50-d1dca1788adc",
    "owner_user_id": "user_01K4EX0BRXHNNGCRVT2TPNK07W",
    "name": "Applied volume by currency (30d)",
    "description": "APPLIED transaction counts by currency",
    "sql": "SELECT currency, COUNT(*) AS txn_count FROM transactions GROUP BY currency LIMIT 1000",
    "range_mode": "rolling",
    "rolling_days": 30,
    "created_at": "2026-08-12T09:28:16.864765Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "FORBIDDEN",
    "message": "lake query mutation is not permitted"
  }
}

Start Here

Deployments

Proxy & data

Data lake

AI integrations

Audit

Alerts

Billing

Authorization

Path

Body

Response

Need help?

​Authorization

​Path

​Body

​Response

​Need help?

Authorization

Path

Body

Response

Need help?