Skip to main content
POST/analytics/{datasetSlug}/schedules/{scheduleId}/reattest

Re-attest Schedule

Confirms the schedule is still wanted: resets its attestation to now and, optionally, sets a new reattestIntervalDays (7, 30, 90 or 365).

A paused schedule resumes.

Returns the schedule with its new expiresAt.

Only a person can re-attest: a service, workload or extension token gets 403 K9O_RBAC_DENY (reason: human_only); a personal access token acts as its person.

Requires the datasets:write permission (PROJECT_ADMIN or PROJECT_AUTHOR by default).

Callers must be members of the project (an organization role alone does not grant access); project service tokens and extension tokens cannot call it.

Parameters
datasetSlug *path

The Dataset's slug.

scheduleId *path

The id of the schedule to re-attest (msch_...), as create and list return it.

It must belong to the dataset in the path.

projectSlug *path

The project's slug: the path segment after @.

It is unique within the org.

Request body
reattestIntervalDaysany

A new attestation window in days: 7, 30, 90 or 365.

Omit it to keep the schedule's current window.

One of: 7
or: 30
or: 90
or: 365
Responses
HTTPK9O CodeDescription
200Success
400K9O_INVALID_REQUEST_SHAPEThe request body does not match the schema.
401K9O_UNAUTHENTICATEDThe caller is not signed in.
403K9O_ACCESS_DENIEDThe caller is not a member of this project; an organization role alone does not grant access.
403K9O_IAM_POLICY_DENIEDThe caller's role or IAM policy does not grant datasets:write.
403K9O_RBAC_DENYOnly a person can re-attest; service, workload and extension tokens are refused (reason human_only). A session is required to re-attest a schedule: a personal access token alone is refused with `context.reason` `session_required`, and a service, workload or extension token with `human_only`.
404K9O_NOT_FOUNDThe project was not found for this caller (project service tokens and extension tokens cannot call this endpoint).
Response body (200)
data *object

The schedule, with its new attestation.

id *string

The schedule's id (msch_...).

datasetSlug *string

The dataset each run writes to.

sourceCollection *string

The collection each run snapshots.

intervalSeconds *integer

Seconds between runs.

enabled *boolean

Whether the schedule is set to run.

reattestIntervalDays *integer

How many days each attestation lasts: 7, 30, 90 or 365.

attestedAt *string <date-time>

When a person last confirmed the schedule (created or re-attested it).

expiresAt *string <date-time>

attestedAt plus reattestIntervalDays.

After it the schedule stops running until it is re-attested; it isn't deleted.

attestationStatus *"active" | "expiring_soon" | "expired"

expiring_soon within 14 days of expiresAt, expired after it.

lastRunAt *any

When the schedule last ran.

Null if it has never run.

One of: string <date-time>
or: null
lastRunStatus *any

How the last run ended: ok, error, stale_principal_denied (the person who configured it no longer has write access to the dataset) or attestation_expired.

Null if it has never run.

One of: string
or: null
nextRunAt *string <date-time>

When the schedule is next due.

createdAt *string <date-time>

When the schedule was created.

meta *any
TypeScript
// const k9o = new K9o({ orgSlug: 'playground', projectSlug: 'storefront', apiKey: 'k9o_…' })
const { data } = await k9o.analytics.schedules.reattest('<datasetSlug>', '<scheduleId>', {})

Showing example in TypeScript

Request example
{
  "reattestIntervalDays": 7
}
Response example (200)
{
  "data": {
    "id": "string",
    "datasetSlug": "string",
    "sourceCollection": "string",
    "intervalSeconds": 0,
    "enabled": false,
    "reattestIntervalDays": 0,
    "attestedAt": "string",
    "expiresAt": "string",
    "attestationStatus": "active",
    "lastRunAt": "string",
    "lastRunStatus": "string",
    "nextRunAt": "string",
    "createdAt": "string"
  }
}

More in Analytics & Intelligence