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

Cvent Event Cloud Compliance API

These API's provide compliance support for regulated industries.**Communication Compliance** lets you view communication activities across your account.Various written forms of communication are captured. For example, emails, SMS, chat messages, or push notificationscan be downloaded for archival or analysis.

Cvent Event Cloud Compliance API is one of 55 APIs that Cvent Event Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Compliance. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version ea.

Requests are made against 2 base URLs: https://api-platform.cvent.com/ea, https://api-platform-eur.cvent.com/ea.

4 operations 3 paths 19 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
ea
Base URL
https://api-platform.cvent.com
Authentication
OAuth 2.0, OAuth 2.0, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 4

Cvent Event Cloud Compliance API declares 4 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2.authorizationCode) using the authorizationCode flow, exposing 205 scopes. It supports OAuth 2.0 (OAuth2.clientCredentials) using the clientCredentials flow, exposing 235 scopes. An API key is passed in the header as Authorization (CallbackApiKeyAuth). It accepts HTTP basic authentication (CallbackBasicAuth).

  • OAuth2.authorizationCode — OAuth2 Authorization Code Flow.
  • OAuth2.clientCredentials — OAuth2 Client Credentials Flow.
  • CallbackApiKeyAuth — This security scheme is used to indicate that Cvent should use API Key auth when invoking your callback. This scheme is only supported for callback operations,…
  • CallbackBasicAuth — This security scheme is used to indicate that Cvent should use basic auth when invoking your callback. This scheme is only supported for callback operations, a…

Paths & Operations 4

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

Compliance 4

These API's provide compliance support for regulated industries. Communication Compliance lets you view communication activities across your account. Various written forms of comm…

GET
/logs/communications/configuration
Get Communication Config
getConfiguration → 200400401403429
PUT
/logs/communications/configuration
Update Communication Config
updateConfiguration body → 200201400401403429
GET
/logs/communications/messages
List Communication
getCommunicationLogMessages 5 params → 200400401403429
POST
/logs/communications/messages/filter
List Communication
filterCommunicationLogMessages 4 params body → 200400401403429

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are communication-log-message.json (6 properties), paging.json (6 properties), question.json (5 properties), pagination-links.json (3 properties). Each schema is shown below with its type and property counts.

attendee.json
object
Attendee details
1 property 1 required
CommunicationConfiguration
object
Communication compliance settings e.g. Configure which communication types will be tracked and logged for this account.
1 property 1 required
link.json
object
Represents a link to a related resource.
1 property 1 required
channel.json
object
The channel details associated with the chat.
1 property 1 required
chat-reaction.json
object
A reaction to a message
1 property 1 required
chat-message-details.json
object
Chat message details such as the ID of this message
2 properties 1 required
ErrorResponse
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
communication-log-message-type.json
string
The type of communication log message.
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
question.json
object
Question details
5 properties 1 required
communication-log-message.json
object
A communication log message.
6 properties 4 required
chat-type.json
string
The chat type
chat-action-type.json
string
The user action that just occurred
ErrorResponseBase
object
Represents an error response with no additional details.
3 properties 2 required
session-qa-action-type.json
string
The user action that just occurred. question.asked - A question was asked. question.upvoted - A question was upvoted. question.statusUpdated - The status of a…
attachment.json1
object
A message attachment.
1 property 1 required
pagination-links.json
object
Represents pagination links for navigating between pages of data.
3 properties
CommunicationLogMessagePaginatedResponse
object
A single page of communication log messages
2 properties 2 required
filter
object
A filter which is sent through the body of the request.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cvent-event-cloud-compliance-api-openapi.yml Raw ↑

Other APIs Cvent Event Cloud publishes across the network.

Cvent Platform REST API (Event Cloud)
Cvent Event Cloud Attendees API
Cvent Event Cloud Contacts API
Cvent Event Cloud Events API
Cvent Event Cloud Sessions API
Cvent Event Cloud Appointments API
Cvent Event Cloud Attendee Activities API
Cvent Event Cloud Attendee Insights API
Cvent Event Cloud Attendee Messages API
Cvent Event Cloud Audience Segments API
Cvent Event Cloud Authentication API
Cvent Event Cloud Badge Print Job API
Where this information came from

This is an independent, third-party profile of Cvent Event Cloud Compliance 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.