CloudBees · Schema
api.v4.RunForUpdate
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 |
|---|---|---|
| runNumber | integer | run number, uniquely identifies an execution of a workflow |
| url | string | run URL in the original external system |
| 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) |
| endedAt | string | run end timestamp |
| 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 |
JSON Schema
{
"$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-update-schema.json",
"title": "api.v4.RunForUpdate",
"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.RunForUpdate",
"type": "object",
"properties": {
"runNumber": {
"type": "integer",
"description": "run number, uniquely identifies an execution of a workflow",
"format": "int32"
},
"url": {
"type": "string",
"description": "run URL in the original external system"
},
"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)"
},
"endedAt": {
"type": "string",
"description": "run end timestamp",
"format": "date-time"
},
"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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cloudbees-api-v4-run-for-update"
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.