Skip to main content
POST
Start a run

Authorizations

cc-key
string
header
required

API key-based authentication. Provide your CloudCruise API key in the cc-key header.

Body

application/json

Configuration for starting a new workflow execution.

Vault Entry References

When workflows require authentication, vault entries are referenced through input variables using their permissioned_user_id:

Single Credential

Pooled Credentials (Load Balancing)

Pooled Credential Benefits:

  • Automatic load balancing across multiple accounts
  • Round-robin selection for optimal distribution
  • Fault tolerance if one credential becomes unavailable
  • Respects individual credential concurrency limits
  • Helps prevent rate limiting on target websites

The alias names (e.g., "USER") are defined in your workflow's vault_schema configuration.

workflow_id
string
required

Unique identifier for the workflow to execute

run_input_variables
Input Variables · object
required

Variables required by the workflow for execution. This includes both regular workflow inputs and vault entry references.

Vault Entry References: When your workflow requires authentication, reference vault entries using their permissioned_user_id:

  • Single credential: "USER": "a1b2c3d4-5678-90ab-cdef-1234567890ab"
  • Pooled credentials: "USER": ["a1b2c3d4-5678-90ab-cdef-1234567890ab", "b2c3d4e5-6789-01bc-def2-234567890abc", "c3d4e5f6-789a-12cd-ef34-34567890abcd"]
  • All credentials for the domain: "USER": []

Pooled Credentials: Provide multiple user IDs as an array to enable automatic load balancing and rotation:

  • CloudCruise uses round-robin selection to distribute runs across available credentials
  • Helps prevent rate limiting and provides fault tolerance
  • Respects each credential's concurrency limits and session settings

Domain-Wide Pool: Pass an empty array to pool every vault entry in your workspace for the alias's domain (as set in the workflow's vault_schema), without listing ids. The alias key must still be present. If no entries exist for the domain, the request fails with a 400 error.

The alias names (e.g., "USER") are defined in your workflow's vault_schema configuration.

dry_run
object
notifications
object
webhook
Webhook Metadata · object

Webhook configuration for receiving execution event notifications. Supports:

  • Custom metadata inclusion
  • Event type filtering
  • Configurable validity periods (in seconds)
priority_level
enum<string>
default:LOW

Execution priority of the run. Priority applies across workflows: when runs compete for the same resources, e.g. a vault entry at its concurrency limit, HIGH runs get them first, then MEDIUM, then LOW. A run waiting for an unavailable resource does not hold back lower-priority runs whose resources are available, and running runs are never interrupted.

Credential pools do not need to match. If workflow A's HIGH runs use the pool [1, 2, 3] and workflow B's LOW runs use [3, 4], B can always use vault entry 4, but gets vault entry 3 only once A has no runs waiting.

If higher-priority runs keep arriving, lower-priority runs competing with them can wait indefinitely.

If omitted, runs default to LOW.

Available options:
LOW,
MEDIUM,
HIGH
encrypted_keys
string[]

Optional list of run_input_variables keys that are encrypted with your workspace AES key.

force_refresh
boolean
default:false

Force-refresh workflow and encryption key caches before starting the run.

capture_console_logs
boolean
default:false

Capture browser console logs during execution.

send_connection_string
boolean
default:false

Include live-view connection details in run execution events when available.

client_id
string

Optional client identifier used by SDKs to bind SSE event streams to this run.

debug
boolean
default:false

When enabled, captures an HTML page snapshot for every node executed in the workflow and records the run's network traffic. Snapshots are retrieved with the debug snapshots endpoint, traffic with the run network endpoint. Network traffic is recorded on workers with network capture.

Debug mode is useful for troubleshooting workflow failures, inspecting the DOM state at each step, and verifying that the browser agent is navigating correctly.

additional_context
Additional Context · object

Optional JSON data that provides additional context to help the maintenance agent handle unexpected scenarios, particularly useful for form filling workflows. When a website unexpectedly requests additional information not covered by the input_variables, this field can be used to provide the extra data needed to complete the form. For example, if a form suddenly asks for a secondary phone number or additional verification details, this context can be used to supply that information. The maintenance agent will use this context to resolve such edge cases and ensure successful form completion.

workflow_version
string

Pin the run to a tagged release by an exact semver version or a range, e.g. "1.2.3", "^1.2.3", "~1.2.3", "1.x", or ">=1.2.3 <2.0.0". The highest tagged release satisfying the range is used. This is the recommended way to pin a run to a specific version — every saved workflow version is tagged with a release automatically. At most one of workflow_version, workflow_version_number, or workflow_branch_id may be given. See Workflow Versioning for what each version bump means and which pin to choose.

workflow_version_number
integer

Legacy — prefer workflow_version for new integrations. Pins the run to the highest tagged release with this major version, i.e. N behaves like workflow_version "N.x.x". Workflows versioned before semantic versions were introduced had their version number N become N.0.0, so pins to those versions keep resolving to the same version until a newer N.x.x is saved. If not provided, the default branch's latest version is used. At most one of workflow_version, workflow_version_number, or workflow_branch_id may be given.

workflow_branch_id
string<uuid>

Pin the run to a branch's current head version. If not provided, the workflow's default branch is used. At most one of workflow_version, workflow_version_number, or workflow_branch_id may be given.

Response

Browser agent run initiated

session_id
string

Unique identifier for the workflow execution session