Skip to main content

​
List schedules

Required scope: schedules:read

​
Create a schedule

A schedule requires cron_expression, timezone, and at least one target in domain_ids, repository_ids, upload_ids, or internal_targets.
Required scope: schedules:write With also_run_now: false, this creates the recurring schedule without launching or charging a scan. With also_run_now: true, the immediate run goes through the same pre-launch credit check as an ordinary scan. If a non-Enterprise workspace lacks the estimated credits, the endpoint returns HTTP 402 Payment Required; neither the schedule nor the immediate scan is created, and no credits are consumed. Enterprise scans are plan-included. Set supply_chain: true for a free dependency scan schedule. Supply-chain schedules accept repository targets only and require the Enterprise Supply Chain entitlement, but their runs do not consume scan credits. When also_run_now starts a billable scan, retain the Idempotency-Key and reuse the exact request after an interrupted or retryable response. The key is bound to the actor and request for 24 hours, so a retry cannot create or charge a second immediate run. The CLI supplies this key automatically.

​
Get schedule detail

Required scope: schedules:read

​
Get a schedule’s editable configuration

This endpoint returns the full stored configuration of the schedule in a format that you can edit with PATCH. The configuration includes targets, prompts, test users, headers, scope, timing, notifications, and uploads. The response gives stored secrets (passwords, TOTP seeds, and header values) as metadata only, not in plaintext.
Required scope: schedules:read

​
Pause a schedule

To resume, use {"action": "resume"}. You can also update the schedule configuration (name, cron_expression, timezone, targets) in the same PATCH request. Required scope: schedules:write

​
Delete a schedule

Required scope: schedules:write

​
Trigger a schedule immediately

Run a scheduled pentest configuration immediately, before the next cron interval:
Required scope: schedules:write The trigger uses the stored scope estimate. If a non-Enterprise workspace lacks enough credits, it returns HTTP 402 Payment Required, creates no scan, and consumes no credits. The CLI reports this as exit code 5. Enterprise runs are credit-exempt. Recurring fires also check the wallet before launch. A run that cannot be funded is skipped rather than launched without a charge. If automatic top-up is enabled, Strix may first try the configured top-up policy; otherwise add credits before the next fire. Manual triggers use the same 24-hour idempotency contract as scan creation. Reuse the exact key and request after an ambiguous response. A delayed or duplicate queue delivery is collapsed before billing or launch.