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 notifications can be downloaded for archival or analysis.

Operations 4

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /logs/communications/configuration Get communication compliance settings · Get Communication Config #
Ask an LLM
“Which communication types is my account recording in the compliance log?”
“Where can I see the communication log configuration for my account?”
Tell an agent
Show my communication compliance configuration.
Get which message types are enabled for communication logging.
PUT /logs/communications/configuration Change which communications get logged · Update Communication Config #
Ask an LLM
“Can I choose which types of messages are recorded in the communication log?”
“How do I turn on logging for more communication types?”
Tell an agent
Set the logged communication types to {enabledMessageTypes}.
Update the compliance config so only {enabledMessageTypes} are recorded.
GET /logs/communications/messages List communication log messages · List Communication #
Ask an LLM
“What emails and messages has my account sent, for compliance records?”
“Can I pull communication log messages between two dates without a filter?”
Tell an agent
List communication log messages sent after {after} and before {before}.
List logged communications matching {filter}.
POST /logs/communications/messages/filter Search the communication log with a body filter · List Communication #
Ask an LLM
“Can I search the communication log with a long filter in the request body?”
“Is there a POST search over logged messages?”
Tell an agent
Search the communication log using body filter {filter}.
Post filter {filter} to find logged messages after {after}.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/cvent-event-cloud:cvent-event-cloud-compliance-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

cvent-event-cloud-compliance-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cvent REST Compliance API
  description: '# Introduction

    The Cvent API Platform is built around REST.'
  contact:
    name: Cvent Development Platform
    url: https://developers.cvent.com/
  version: ea
servers:
- url: https://api-platform.cvent.com/ea
- url: https://api-platform-eur.cvent.com/ea
tags:


# --- truncated at 32 KB (58 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-compliance-api-openapi.yml