Webex · Schema

GetContactListsResponse

Response containing contact lists within a campaign, including contact counts and dialer status breakdown for each list.

CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing

Properties

Name Type Description
outcome string Outcome of the operation
statusCode integer 0 for success, non-zero for failure or validation failure
contactLists array List of contact lists
View JSON Schema on GitHub

JSON Schema

webex-get-contact-lists-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/webex/json-schema/webex-get-contact-lists-response-schema.json",
  "title": "GetContactListsResponse",
  "description": "Response containing contact lists within a campaign, including contact counts and dialer status breakdown for each list.",
  "x-generated": "2026-11-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/webex-contact-list-management-api-openapi.yml#/components/schemas/GetContactListsResponse",
  "type": "object",
  "required": [
    "outcome",
    "statusCode",
    "contactLists"
  ],
  "properties": {
    "outcome": {
      "type": "string",
      "enum": [
        "Success",
        "Failure"
      ],
      "description": "Outcome of the operation"
    },
    "statusCode": {
      "type": "integer",
      "description": "0 for success, non-zero for failure or validation failure"
    },
    "contactLists": {
      "type": "array",
      "description": "List of contact lists",
      "items": {
        "$ref": "#/$defs/ContactListInfo"
      }
    }
  },
  "$defs": {
    "ContactListInfo": {
      "type": "object",
      "description": "Contact list details and contact counts by processing and dialer status. Count fields are `0` when counts are not yet available for a newly created list.",
      "properties": {
        "contactListId": {
          "type": "string",
          "description": "Contact list ID within the campaign."
        },
        "contactListStatus": {
          "type": "string",
          "description": "Contact list status (for example: Active, Expired, UploadFailed)."
        },
        "contactListSource": {
          "type": "string",
          "description": "How the contact list was created (for example, API, SFTP, ManualFile)."
        },
        "contactListSourceFileName": {
          "type": "string",
          "description": "Source file name for the contact list upload."
        },
        "contactListCountsTimestampUtc": {
          "type": "string",
          "format": "date-time",
          "description": "UTC timestamp when the counts were last updated."
        },
        "processedContactsCount": {
          "type": "integer",
          "description": "Total contacts processed for this contact list."
        },
        "invalidContactsCount": {
          "type": "integer",
          "description": "Number of invalid contacts."
        },
        "validContactsCount": {
          "type": "integer",
          "description": "Derived: `processedContactsCount` − `invalidContactsCount`."
        },
        "eligibleContactsCount": {
          "type": "integer",
          "description": "Derived: `processedContactsCount` − `invalidContactsCount` − DNC-suppressed contacts."
        },
        "freshContactsCount": {
          "type": "integer",
          "description": "Number of contacts in Fresh state."
        },
        "openContactsCount": {
          "type": "integer",
          "description": "Number of contacts in Open state."
        },
        "closedContactsCount": {
          "type": "integer",
          "description": "Number of contacts in Closed state."
        },
        "errorsContactsCount": {
          "type": "integer",
          "description": "Number of contacts in Error state."
        },
        "readyForDialerContactsCount": {
          "type": "integer",
          "description": "Number of contacts ready to be sent to the dialer."
        },
        "sentToDialerAwaitingOutcomeContactsCount": {
          "type": "integer",
          "description": "Number of contacts sent to the dialer and awaiting an outcome."
        },
        "expiredContactsCount": {
          "type": "integer",
          "description": "Number of expired contacts."
        },
        "blockedContactsCount": {
          "type": "integer",
          "description": "Number of blocked contacts."
        },
        "closedTransferredToChainedCampaignContactsCount": {
          "type": "integer",
          "description": "Number of contacts closed and transferred to a chained campaign."
        },
        "dateOfCreation": {
          "type": "string",
          "format": "date-time",
          "description": "Date and time the contact list was created, in the campaign time zone."
        },
        "dateOfActivation": {
          "type": "string",
          "format": "date-time",
          "description": "Date and time the contact list was activated."
        },
        "dateOfExpiry": {
          "type": "string",
          "format": "date-time",
          "description": "Date and time the contact list expires."
        }
      }
    }
  }
}

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-get-contact-lists-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.