CloudBees · Schema

api.v4.RunForCreate

Run represents an external CI/CD run from a third-party tool.

CI/CDContinuous DeliveryContinuous IntegrationDeveloper ToolsDevOpsFeature FlagsFeature ManagementJenkinsRelease OrchestrationSoftware Delivery

Properties

Name Type Description
scmRef string The SCM ref for this run; can be a branch, a tag, etc. Must use the full git ref format (e.g.: refs/heads/main)
workflowName string the name of the workflow that is being executed
runNumber integer run number, uniquely identifies an execution of a workflow
toolType string CI/CD tool that produced this run; accepted values: ARGO_CD, CLOUDBEES_CI, HARNESS, JENKINS, UNIFY, CLOUDBEES, GITHUB This field will default to UNKNOWN if the tool doesn't match one of the accepted v
runAttempt integer run attempt, used in engines like GitHub Actions to distinguish between multiple executions of a workflow
url string run URL in the original external system
trigger string what triggered the run; accepted values: PUSH, PULL_REQUEST, WORKFLOW_DISPATCH, SCHEDULE
actorName string who triggered the run
actorEmail string email address of the user who triggered the run
status string run status; accepted values: PENDING, PAUSED, STARTED, FAILED, ERRORED, ABORTED, SUCCEEDED, PENDING_APPROVAL, TIMED_OUT, APPROVED, REJECTED, APPROVAL_TIMED_OUT, SKIPPED, UNSCHEDULED, UNSTABLE
statusMessage string run status message (normally specifying the failure cause)
startedAt string run start timestamp
endedAt string run end timestamp
changeRequestTitle string title of the change request that triggered the run
changeRequestTargetBranch string target branch of the change request
commitSha string commit SHA that triggered the run
commitMessage string commit message of the commit that triggered the run. The value of this field, if present, overrides change_request_title
externalParentFlow string external system identifier to group related runs under a common pipeline or workflow
statusReason string status_reason is "POLICY" when a policy gate caused the current status, otherwise empty. Note: CloudBees-native runs never report PENDING_APPROVAL as their run status on this API, so in practice this
View JSON Schema on GitHub

JSON Schema

cloudbees-api-v4-run-for-create-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/cloudbees/main/json-schema/cloudbees-api-v4-run-for-create-schema.json",
  "title": "api.v4.RunForCreate",
  "description": "Run represents an external CI/CD run from a third-party tool.",
  "x-generated": "2026-10-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/cloudbees-runs-api-openapi.yml#/components/schemas/api.v4.RunForCreate",
  "required": [
    "scmRef",
    "workflowName",
    "toolType",
    "url",
    "trigger",
    "actorName",
    "status",
    "startedAt",
    "commitSha"
  ],
  "type": "object",
  "properties": {
    "scmRef": {
      "type": "string",
      "description": "The SCM ref for this run; can be a branch, a tag, etc. Must use the full git ref format (e.g.: refs/heads/main)"
    },
    "workflowName": {
      "type": "string",
      "description": "the name of the workflow that is being executed"
    },
    "runNumber": {
      "type": "integer",
      "description": "run number, uniquely identifies an execution of a workflow",
      "format": "int32"
    },
    "toolType": {
      "type": "string",
      "description": "CI/CD tool that produced this run; accepted values: ARGO_CD, CLOUDBEES_CI, HARNESS, JENKINS, UNIFY, CLOUDBEES, GITHUB\n This field will default to UNKNOWN if the tool doesn't match one of the accepted values"
    },
    "runAttempt": {
      "type": "integer",
      "description": "run attempt, used in engines like GitHub Actions to distinguish between multiple executions of a workflow",
      "format": "int32"
    },
    "url": {
      "type": "string",
      "description": "run URL in the original external system"
    },
    "trigger": {
      "type": "string",
      "description": "what triggered the run; accepted values: PUSH, PULL_REQUEST, WORKFLOW_DISPATCH, SCHEDULE"
    },
    "actorName": {
      "type": "string",
      "description": "who triggered the run"
    },
    "actorEmail": {
      "type": "string",
      "description": "email address of the user who triggered the run"
    },
    "status": {
      "type": "string",
      "description": "run status; accepted values: PENDING, PAUSED, STARTED, FAILED, ERRORED, ABORTED, SUCCEEDED, PENDING_APPROVAL, TIMED_OUT, APPROVED, REJECTED, APPROVAL_TIMED_OUT, SKIPPED, UNSCHEDULED, UNSTABLE"
    },
    "statusMessage": {
      "type": "string",
      "description": "run status message (normally specifying the failure cause)"
    },
    "startedAt": {
      "type": "string",
      "description": "run start timestamp",
      "format": "date-time"
    },
    "endedAt": {
      "type": "string",
      "description": "run end timestamp",
      "format": "date-time"
    },
    "changeRequestTitle": {
      "type": "string",
      "description": "title of the change request that triggered the run"
    },
    "changeRequestTargetBranch": {
      "type": "string",
      "description": "target branch of the change request"
    },
    "commitSha": {
      "type": "string",
      "description": "commit SHA that triggered the run"
    },
    "commitMessage": {
      "type": "string",
      "description": "commit message of the commit that triggered the run. The value of this field, if present, overrides change_request_title"
    },
    "externalParentFlow": {
      "type": "string",
      "description": "external system identifier to group related runs under a common pipeline or workflow"
    },
    "statusReason": {
      "type": "string",
      "description": "status_reason is \"POLICY\" when a policy gate caused the current status, otherwise empty.\n Note: CloudBees-native runs never report PENDING_APPROVAL as their run status on this API,\n so in practice this identifies a policy-caused failure."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cloudbees-api-v4-run-for-create"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.