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 Campaigns API

Planners use eMarketing campaigns to contact an audience, such as newsletters, press releases, or product updates. Campaign emails are used as newsletters, promotions, advertisements, or marketing messages. Use these APIs to send an email and get historical data about your campaigns.

Cvent Campaigns API is one of 65 APIs that Cvent publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Campaigns. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 4 paths, and defines 20 schemas. It is described by OpenAPI 3.0.2, 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 4 paths 20 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Cvent Campaigns API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2.clientCredentials) using the clientCredentials flow, exposing 238 scopes. It supports OAuth 2.0 (OAuth2.authorizationCode) using the authorizationCode flow, exposing 208 scopes.

  • OAuth2.clientCredentials — OAuth2 Client Credentials Flow.
  • OAuth2.authorizationCode — OAuth2 Authorization Code Flow.

Paths & Operations 4

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

Campaigns 4

Planners use eMarketing campaigns to contact an audience, such as newsletters, press releases, or product updates. Campaign emails are used as newsletters, promotions, advertiseme…

GET
/campaigns
List eMarketing Campaigns
getCampaigns 5 params → 200400401403429
GET
/emarketing/campaigns/{campaignId}/email-templates
List Email Templates
getEmailTemplates 5 params → 200400401403404429
POST
/emarketing/emails
Send Email To Recipients
sendEMarketingEmails body → 202400401403429
GET
/emarketing/emails/{emailRequestId}/status
List Emarketing Email Status
getEmarketingEmailStatus 1 param → 200400401403404429

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are paging.json (6 properties), campaign-data.json (6 properties), send-email-response (5 properties), send-email-event-response (4 properties). Each schema is shown below with its type and property counts.

email-template-data.json
object
Response object to get email templates for an unique campaign.
2 properties
pagination-links.json
object
Represents pagination links for navigating between pages of data.
3 properties
attendee-response.json
object
Response object indicating the status of send email request for a particular attendee.
3 properties 2 required
send-email-event-response
object
Response object containing a request ID and a list of all email responses sent to attendees.
4 properties 4 required
send-email-status.json
string
It is used to denote the status of the sent email.
ErrorResponseBase1
object
Represents an error response with no additional details.
3 properties 2 required
email-template-paginated-response
object
The response from a request to get the list of email templates. This includes the paging object as well as the collection of email template.
2 properties 2 required
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
send-email-request
object
Request object to send an email to one or more eMarketing campaign recipients.
2 properties 2 required
campaign-list-paginated-response
object
The response from a request to get the list of campaign. This includes the paging object as well as the collection of campaign data.
2 properties 2 required
ErrorResponse-12
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
event.json3
object
Details of the event.
1 property 1 required
send-email-emarketing-response
object
Response object containing a request ID and a list of all email responses sent to recipients.
2 properties 2 required
campaign-data.json
object
Campaign data model.
6 properties
link.json
object
Represents a link to a related resource.
1 property 1 required
email.json
object
Details of an email to be send.
1 property 1 required
send-email-request-status.json
string
Denotes the status of the send email request.
send-email-response
object
Response object containing a request ID and a list of all email responses sent to recipients.
5 properties 3 required
recipients-response.json
object
Response object indicating the status of send email request for a particular recipient.
3 properties 2 required
recipients-request.json
object
Recipient contains the recipient ID of a recipient.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cvent-campaigns-api-openapi.yml Raw ↑

Other APIs Cvent publishes across the network.

Cvent REST API
Cvent Webhooks API
Cvent Supplier Network (CSN) API
Cvent Passkey RegLink API
Cvent SOAP API (Legacy)
Cvent Custom Widgets API
Cvent Single Sign-On (SSO) Integration
Cvent White Label API
Cvent Salesforce App
Cvent Attendees API
Cvent Contacts API
Cvent Events API
Where this information came from

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