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 Journey - Profile Creation & Insights API

The Journey - Profile Creation & Insights API API from Webex — 11 operation(s) for journey - profile creation & insights api.

Webex Journey - Profile Creation & Insights API is one of 192 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

14 operations 11 paths 26 schemas 1 DELETE11 GET1 POST1 PUT

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 Journey - Profile Creation & Insights 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 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 11 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Journey - Profile Creation & Insights API 14
GET
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}/template-id/{templateId}
Get A specific Template searched by template id
getTemplatebyId 2 params → 200404500
PUT
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}/template-id/{templateId}
Update existing ProfileViewTemplate
updateProfileViewTemplate 2 params body → 200400500
DELETE
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}/template-id/{templateId}
Delete Template by template Id
deleteTemplatebyId 2 params → 200404500
GET
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}
Get All Template Details
getAllTemplates 6 params → 200404500
POST
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}
Create Template
createTemplate 1 param body → 201400404500
GET
/admin/v1/api/profile-view-template/workspace-id/{workspaceId}/template-name/{templateName}
Get A specific Template searched by template name
getTemplatebyName 2 params → 200404500
GET
/v1/api/progressive-profile-view/workspace-id/{workspaceId}/person-id/{personId}/template-name/{templateName}
Historic Progressive Profile View by Template Name
getProgressiveProfileViewByTemplateName 3 params → 200400404500
GET
/v1/api/progressive-profile-view/workspace-id/{workspaceId}/person-id/{personId}/template-id/{templateId}
Historic Progressive Profile View
getProgressiveProfileView 3 params → 200400404500
GET
/v1/api/progressive-profile-view/workspace-id/{workspaceId}/identity/{identity}/template-name/{templateName}
Historic Progressive Profile View By Template Name
getProgressiveProfileViewByIdentityAndTemplateName 3 params → 200400404500
GET
/v1/api/progressive-profile-view/workspace-id/{workspaceId}/identity/{identity}/template-id/{templateId}
Historic Progressive Profile View By Template Id
getProgressiveProfileViewByIdentityAndTemplateId 3 params → 200400404500
GET
/v1/api/progressive-profile-view/stream/workspace-id/{workspaceId}/identity/{identity}/template-name/{templateName}
Stream Progressive profile Views By Template Name
streamProgressiveProfileViewsByTemplateName 3 params → 200404409429500
GET
/v1/api/progressive-profile-view/stream/workspace-id/{workspaceId}/identity/{identity}/template-id/{templateId}
Stream Progressive profile Views By Template Id
streamProgressiveProfileViews 3 params → 200404409429500
GET
/v1/api/events/workspace-id/{workspaceId}
Historic Journey Events
historicEvents 8 params → 200404409429500
GET
/v1/api/events/stream/workspace-id/{workspaceId}/identity/{identity}
Stream Events By Identity
streamEventsByIdentity 4 params → 200404409429500

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are ProfileViewAttributeRequestModel (12 properties), ProfileViewAttributeResponseModel (12 properties), JourneyCloudEventModel (10 properties), TemplateResponseModel (9 properties). Each schema is shown below with its type and property counts.

ProgressiveProfileViewMetaDataModel
object
4 properties
ProfileResponse
object
2 properties
RulesDocument
object
Configuration details of the Rules based on which the Action will be triggered
2 properties
BaseMetaResponseEnvelope
object
Meta information of the response
1 property
eventData
object
Event Data
6 properties
ApiError500
object
5 properties 1 required
Rules
object
Configuration details of the Rules
2 properties
ProgressiveProfileViewAttributes
object
4 properties
ProfileViewSystemMetadata
object
ProfileViewSystemMetdata
1 property
JourneyEventStreamMetaDataModel
object
4 properties
ApiError400
object
5 properties 1 required
ProfileViewAttributeRequestModel
object
Create or Update Attribute of a ProfileViewTemplate
12 properties 10 required
TemplateResponseModel
object
Template Response Model
9 properties
ProgressiveProfileViewModel
object
Create Or Update Progressive Profile View
8 properties 4 required
JourneyCloudEventModel
object
Journey Cloud Event Model
10 properties 8 required
ApiError429
object
5 properties 1 required
WidgetAttributesResponseModel
object
WidgetAttributes
1 property
ApiError404
object
5 properties 1 required
ProgressiveProfileViewStreamModel
object
2 properties
WidgetAttributesRequestModel
object
Create or Update WidgetAttributes
1 property
ApiError409
object
5 properties 1 required
ProfileViewAttributeResponseModel
object
Attributes under an ProfileViewTemplate
12 properties
JourneyEventStreamModel
object
2 properties
CreateOrUpdateTemplateModel
object
Create Or Update Template
2 properties 2 required
ProfileGetResponse
object
2 properties
JourneyActionTriggerHistory
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-journey-profile-creation-insights-api-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 Journey - Profile Creation & Insights 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.