Get a repository's Continuous Security schedule
const url = 'https://zkao.io/api/v1/projects/example/repositories/example/continuous-testing';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://zkao.io/api/v1/projects/example/repositories/example/continuous-testing \ --header 'Authorization: Bearer <token>'Requires scope: read. Continuous Security scans one branch on a schedule paid from a monthly budget. With no schedule on the branch, enabled is false and the schedule fields are null. The recommended monthly budget supports ongoing analysis. The minimum funds one useful analysis step. availableFeatures lists the analyses this branch offers. enabledFeatures lists the branch’s selected analyses, including while paused.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”The scheduled branch. Defaults to the repository’s default branch.
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" }}