Schedule saved query

PUT

data

lake

queries

{query_id}

schedule

curl -X PUT 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94/schedule' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true
  }'

{
  "data": {
    "id": "lake_query_schedule_6e6feddd-930b-4e38-8ba1-1a3eee659bb3",
    "query_id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true,
    "next_run_at": "2026-08-16T13:00:00Z",
    "created_at": "2026-08-15T11:02:41.112739Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "INVALID_REQUEST",
    "message": "cron_expression must be a valid five-field cron expression"
  }
}

Create or replace the schedule on a saved lake query. When the cron fires, Cloud creates a query run: one execution of the last saved SQL and date range. That run stores a result preview. The schedule does not send email or webhook notifications. Only the query owner or an admin can set a schedule. cron_expression is a five-field cron (minute hour day-of-month month day-of-week). timezone is an IANA timezone such as America/New_York.

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 PUT 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94/schedule' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true
  }'

string

required

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

Body

string

required

Five-field cron that says when Cloud starts a query run (minute hour day-of-month month day-of-week). Example: 0 9 * * * is every day at 09:00 in timezone.

string

required

IANA timezone Cloud uses to interpret cron_expression, such as America/New_York or UTC. next_run_at is still returned in UTC. For a rolling saved query, Cloud also resolves the date window in this timezone.

boolean

Whether Cloud will fire the schedule. Defaults to true. Send false to keep the schedule stored but skip runs until you enable it again.

Response

{
  "data": {
    "id": "lake_query_schedule_6e6feddd-930b-4e38-8ba1-1a3eee659bb3",
    "query_id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true,
    "next_run_at": "2026-08-16T13:00:00Z",
    "created_at": "2026-08-15T11:02:41.112739Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "INVALID_REQUEST",
    "message": "cron_expression must be a valid five-field cron expression"
  }
}

string

Unique id of this schedule (lake_query_schedule_...).

string

Saved query this schedule belongs to (lake_query_...).

string

Five-field cron Cloud stored. This is when each query run starts, interpreted in timezone.

string

IANA timezone Cloud uses to interpret the cron, such as America/New_York.

boolean

Whether Cloud will fire the schedule. false keeps the schedule stored but skips runs.

timestamp

Next time Cloud will start a query run for this schedule, in UTC.

timestamp

When Cloud last started a query run from this schedule. Omitted until the first fire.

timestamp

When the schedule was first created. A replace keeps this value.

timestamp

When the cron, timezone, or enabled flag was last changed.

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 PUT 'https://api.cloud.blnkfinance.com/data/lake/queries/lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94/schedule' \
  -H 'Authorization: Bearer CLOUD_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true
  }'

{
  "data": {
    "id": "lake_query_schedule_6e6feddd-930b-4e38-8ba1-1a3eee659bb3",
    "query_id": "lake_query_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94",
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York",
    "enabled": true,
    "next_run_at": "2026-08-16T13:00:00Z",
    "created_at": "2026-08-15T11:02:41.112739Z",
    "updated_at": "2026-08-15T11:02:41.112739Z"
  }
}

{
  "error": {
    "code": "INVALID_REQUEST",
    "message": "cron_expression must be a valid five-field cron expression"
  }
}

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?