Cvent Registration Compliance API

These API's provide compliance support for regulated industries. **Communication Compliance** lets you view communication activities across your account for archival or analysis. Various written forms of communication are captured. This includes: emails, SMS, session chats, exhibitor chats, text discussions, 1:1 attendee messaging, group messaging, or push notifications.

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 the communication log configuration · Get Communication Config #
Ask an LLM
“Which communication types is my account recording in the compliance log?”
“Is chat or session Q&A logging turned on for my account?”
Tell an agent
Show my communication compliance configuration.
Tell me which message types the communication log is capturing.
PUT /logs/communications/configuration Choose which communications get logged · Update Communication Config #
Ask an LLM
“How do I turn on logging of chats or emails for compliance?”
“Can I pick exactly which message types go into the communication log?”
Tell an agent
Set the logged communication types to {enabledMessageTypes}.
Record only {enabledMessageTypes} in the communication compliance log.
GET /logs/communications/messages List logged communication messages · List Communication #
Ask an LLM
“What emails, chats and session Q&A messages has my account logged between two dates?”
“Do I have to pass a filter to read the communication log?”
Tell an agent
List communication log messages from {after} to {before}.
List logged messages matching query filter {filter}.
POST /logs/communications/messages/filter Search the communication log with a body filter · List Communication #
Ask an LLM
“Can I send a long filter in the request body to search the communication log?”
“Is there a POST search for logged chats and emails?”
Tell an agent
Search the communication log with body filter {filter}.
Search logged messages between {after} and {before} using body filter {filter}.

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-registration:cvent-registration-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-registration-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 (59 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-registration/refs/heads/main/openapi/cvent-registration-compliance-api-openapi.yml