Webex · Schema

StartJobExecutionStatusObject

CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing

Properties

Name Type Description
id number Unique identifier for each instance of the job.
startTime string Start date and time of the job in UTC format.
lastUpdated string Last update date and time of the job in UTC format after a step execution completion.
statusMessage string Status for the overall steps that are part of the job. * `STARTING` - Job has started. * `STARTED` - Job is in progress. * `COMPLETED` - Job has completed. * `FAILED` - Job has failed. * `UNKNOWN` - J
exitCode string Overall result of the job. * `UNKNOWN` - Job is in progress. * `COMPLETED` - Job has completed. * `FAILED` - Job has failed. * `COMPLETED_WITH_ERRORS` - Job has completed with errors. * `COMPLETED_WIT
createdTime string Creation date and time of the job in UTC format.
timeElapsed string Time elapsed in seconds since the job execution started.
View JSON Schema on GitHub

JSON Schema

webex-startjobexecutionstatusobject-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/StartJobExecutionStatusObject",
  "title": "StartJobExecutionStatusObject",
  "type": "object",
  "required": [
    "id",
    "startTime",
    "statusMessage",
    "createdTime"
  ],
  "properties": {
    "id": {
      "type": "number",
      "example": 332387,
      "description": "Unique identifier for each instance of the job."
    },
    "startTime": {
      "type": "string",
      "example": "2023-05-30T13:04:00.469Z",
      "description": "Start date and time of the job in UTC format."
    },
    "lastUpdated": {
      "type": "string",
      "example": "2023-05-30T13:04:03.574Z",
      "description": "Last update date and time of the job in UTC format after a step execution completion."
    },
    "statusMessage": {
      "type": "string",
      "enum": [
        "STARTING",
        "STARTED",
        "COMPLETED",
        "FAILED",
        "UNKNOWN",
        "ABANDONED"
      ],
      "description": "Status for the overall steps that are part of the job.\n * `STARTING` - Job has started.\n * `STARTED` - Job is in progress.\n * `COMPLETED` - Job has completed.\n * `FAILED` - Job has failed.\n * `UNKNOWN` - Job status is unknown.\n * `ABANDONED` - Job has been abandoned (manually stopped).\n"
    },
    "exitCode": {
      "type": "string",
      "enum": [
        "UNKNOWN",
        "COMPLETED",
        "FAILED",
        "COMPLETED_WITH_ERRORS",
        "COMPLETED_WITH_PENDING_ORDERS"
      ],
      "description": "Overall result of the job.\n * `UNKNOWN` - Job is in progress.\n * `COMPLETED` - Job has completed.\n * `FAILED` - Job has failed.\n * `COMPLETED_WITH_ERRORS` - Job has completed with errors.\n * `COMPLETED_WITH_PENDING_ORDERS` - Job has completed with pending number orders.\n"
    },
    "createdTime": {
      "type": "string",
      "example": "2023-05-30T13:04:00.457Z",
      "description": "Creation date and time of the job in UTC format."
    },
    "timeElapsed": {
      "type": "string",
      "example": "PT2.752S",
      "description": "Time elapsed in seconds since the job execution started."
    }
  }
}

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/webex-startjobexecutionstatusobject"
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.