How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Webex Contact List Management API

Operations for managing contact lists and contacts

Webex Contact List Management API is one of 193 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contact List Management. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 7 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

7 operations 7 paths 14 schemas 2 GET3 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Authentication
OAuth 2.0, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 5

Webex Contact List Management API declares 5 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. It accepts HTTP bearer tokens (JWT) (bearer-key). It accepts HTTP bearer tokens (BEARER_TOKEN_FROM_CI). It accepts HTTP bearer tokens (JWT) (Bearer). It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • Bearer — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — JWT bearer token authentication. Obtain your token from the Webex Developer Portal.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 2 GET, 3 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Contact List Management 7

Operations for managing contact lists and contacts

POST
/v3/campaign-management/campaigns/{campaignId}/contact-list
Create contact list
createContactList 1 param body → 201400
POST
/v3/campaign-management/campaigns/{campaignId}/contact-list/{contactListId}/contacts
Create contacts within a contact list
createContactsInContactList 2 params body → 202400
PATCH
/v3/campaign-management/campaigns/{campaignId}/contact-list/{contactListId}/contacts/{contactId}
Update a contact's status within a contact list
updateContactStatusInContactList 3 params body → 202400
PATCH
/v3/campaign-management/campaigns/{campaignId}/contacts/{contactId}
Update contact status across the campaign chain
updateContactStatusInCampaignChain 4 params body → 200400403404429
PATCH
/v3/campaign-management/campaigns/{campaignId}/contact-list/{contactListId}/status
Update contact list status
updateContactListStatus 2 params body → 200400
GET
/v3/campaign-management/campaigns/{campaignId}/contact-lists
Get Contact Lists within a Campaign
getContactListsInCampaign 3 params → 200400
GET
/v4/campaign-management/campaigns/{campaignId}/contact-lists
Get Contact Lists within a Campaign
getContactListsInACampaign 3 params → 200400

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ContactListInfo (21 properties), ContactCampaignUpdateResult (7 properties), CreateContactListRequest (3 properties), UpdateContactListStatusResponse (3 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Error response
2 properties
UpdateContactResponse
object
3 properties
ContactCampaignUpdateResult
object
Close outcome for one campaign.
7 properties
CreateContactResponse
object
3 properties
UpdateContactListStatusResponse
object
3 properties
ContactListInfo
object
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.
21 properties
CreateContactListRequest
object
3 properties 1 required
GetContactListsResponse
object
Response containing contact lists within a campaign, including contact counts and dialer status breakdown for each list.
3 properties 3 required
CreateContactListResponse
object
3 properties
UpdateContactRequest
object
1 property
CreateContactRequest
object
1 property
UpdateContactStatusWithinCampaignChainRequest
object
2 properties 1 required
UpdateContactListStatusRequest
object
1 property
UpdateContactStatusResponse
object
Result of the "close contact record" request. Each item in records describes the outcome in the target campaign where the contact was found.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-contact-list-management-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
Webex Admin Audit Events API
Webex Agent Personal Greeting Files API
Webex Agent Summaries API
Webex Agent Wellbeing API
Webex Agents API
Webex AI Feature API
Webex API - Domain Management API
Webex Archive Users API
Webex Attachment Actions API
Webex Audio Files API
Webex Authorizations API
Where this information came from

This is an independent, third-party profile of Webex Contact List Management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.