Turn Continuous Security on, change it, or pause it
const url = 'https://zkao.io/api/v1/projects/example/repositories/example/continuous-testing';const options = { method: 'PUT', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"branch":"main","enableFeatures":["formal-verification"]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://zkao.io/api/v1/projects/example/repositories/example/continuous-testing \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "branch": "main", "enableFeatures": [ "formal-verification" ] }'Requires scope: automations:write. Every field is optional. To start a schedule, send enabled: true with the branch and its authorized monthly budget. A new schedule uses defaultMonthlyCredits when no budget is given. The default is a low limit that funds at least one analysis step. When a month’s budget is used, automatic analysis waits until the budget is raised or the month resets. The budget sets the interval smoothly from once a month to twice a day. A budget outside the returned minimum and maximum is refused with 400. Administrators can raise the maximum monthly budget. areaKeys replaces the audit areas runs rotate through, one per run. Use enableFeatures to add analyses or enabledFeatures to replace the selection. Omit both to keep it. A selection sent without enabled or monthlyBudgetCredits requires an existing schedule and returns 409 if none exists. The resulting selection must include at least one analysis that can run on its own. enabled: false pauses the schedule and keeps it. A change re-arms a schedule that had stopped. Each run still needs spendable credits when it launches.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”object
False pauses the schedule; true turns it on or resumes it.
Re-plans the interval and the per-run budget within the returned minimum and maximum.
Replaces the rotation set. An empty array scans the whole repository every run.
Adds the listed analyses to the current selection. Mutually exclusive with enabledFeatures.
Replaces the selection with exactly these analyses. Mutually exclusive with enableFeatures.
The scheduled branch. Defaults to the repository’s default branch.
not matching
Examples
Add formal verification to an existing schedule
{ "branch": "main", "enableFeatures": [ "formal-verification" ]}Start or resume formal verification alone with an approved monthly budget
{ "branch": "main", "enabled": true, "monthlyBudgetCredits": 50000, "enabledFeatures": [ "formal-verification" ]}Responses
Section titled “ Responses ”OK
object
False when Continuous Security is not offered.
False when there is no schedule or it is paused.
Why an enabled schedule is not running: budget_reached when the schedule’s or project’s monthly automation cap is reached, needs_credits when the organization’s credits cannot fund the next run (it resumes on its own once they can), error after repeated failures. Null with no schedule.
The configured monthly spending cap. Legacy schedules derive the budget from their cadence and per-run budget.
Legacy fixed cadence. Null for a custom interval or no schedule. Use intervalHours for the actual interval.
Hours between scheduled runs. Null when no schedule exists.
Audit areas the runs rotate through, one per run, least recently scanned first. Empty means every run scans the whole repository.
Analyses offered on this branch. Empty when Continuous Security is unavailable.
Selected analyses. A branch with no saved selection defaults to bug hunting when Continuous Security is available. A paused schedule keeps its selection.
Credits the branch was charged for Continuous Security since the UTC month began, net of refunds. Counts its analysis steps, change assessments, public-key reviews, agent questions and the planning included in steps.
Runs the schedule launched since the UTC month began.
When the next run becomes due. A past time means within the hour. Null when paused or stopped.
The monthly budget a new schedule gets when the request names none. It funds at least one analysis step.
A monthly budget that funds about four analysis steps, within the minimum and maximum. A suggestion to pass as monthlyBudgetCredits. It is never applied when the request names no budget.
The smallest month that funds one analysis step. Less is refused.
The largest monthly budget currently allowed for the repository. Administrators can raise it.
Example
{ "state": "active", "cadence": "daily", "availableFeatures": [ "bug-hunting" ], "enabledFeatures": [ "bug-hunting" ]}Invalid request
object
object
Budget_below_minimum only: the least the launch could have reserved, in credits. A diff scan’s first scan of a repository also builds its overview, so its minimum is higher.
Example
{ "error": { "code": "unauthorized" }}Missing, malformed, expired, or revoked token
object
object
Budget_below_minimum only: the least the launch could have reserved, in credits. A diff scan’s first scan of a repository also builds its overview, so its minimum is higher.
Example
{ "error": { "code": "unauthorized" }}The token lacks the required scope
object
object
Budget_below_minimum only: the least the launch could have reserved, in credits. A diff scan’s first scan of a repository also builds its overview, so its minimum is higher.
Example
{ "error": { "code": "unauthorized" }}Resource not in this token’s project or repo allowlist
object
object
Budget_below_minimum only: the least the launch could have reserved, in credits. A diff scan’s first scan of a repository also builds its overview, so its minimum is higher.
Example
{ "error": { "code": "unauthorized" }}A compare-and-set (expectedContent) missed: the guidance changed since it was read. Re-read the current guidance and retry.
object
object
Budget_below_minimum only: the least the launch could have reserved, in credits. A diff scan’s first scan of a repository also builds its overview, so its minimum is higher.
Example
{ "error": { "code": "unauthorized" }}