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 Event Features API

EventFeatures related APIs

Cvent Event Cloud Event Features 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 Event Features. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 20 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 4 paths 20 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 Event Features 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 4 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Event Features 4

EventFeatures related APIs

GET
/events/{id}/features
List Event Features
getEventFeatures 5 params → 200400401403404429
PUT
/events/{id}/features/{type}
Update Event Feature
updateEventFeatures 2 params body → 200400401403404429
POST
/events/{id}/features/{type}/launch
Launch Event Feature
launchEventFeatures 2 params body → 204400401403404429
GET
/events/{id}/weblinks
List Event Weblinks
listEventWeblinks 4 params → 200400401403404429

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are event-features-response (8 properties), event-feature.json (8 properties), paging.json (6 properties), pricing-config.json (6 properties). Each schema is shown below with its type and property counts.

feature-tier.json
object
Tier available for the feature
3 properties 1 required
link.json
object
Represents a link to a related resource.
1 property 1 required
event-features-paginated-response
object
Paginated collection of event features.
2 properties 2 required
feature-type.json
string
The type of feature available for a container event. | Value | Description | |-------|-------------| | Website | Allows you to promote your event with a custom…
tier.json
string
Represents the type of license that the user can choose.
event-feature-launch-request
object
Event-features launch request parameters.
1 property
uuid-property
string
A string that has to be a format matching the industry standard uuid
event-features-response
object
Representation of an event's feature along with its properties
8 properties 3 required
ErrorResponse
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
event-feature.json
object
Representation of an event's feature along with its properties
8 properties 3 required
locale.json
string
Locale code
event-weblinks-paginated-response
object
Paginated collection of event weblinks.
2 properties 2 required
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
event-weblink.json
object
Metadata for an event weblink.
4 properties
pricing-config.json
object
Represents the configuration of the event's pricing feature.
6 properties 1 required
feature-update
object
Representation of an event feature update request
4 properties 2 required
launch-feature-type.json
string
These are the types of features used in the event container events that can be launched.
ErrorResponseBase
object
Represents an error response with no additional details.
3 properties 2 required
payment-method-type.json
string
Denotes acceptable payment methods for merchant accounts. Not all options are valid for all merchants.
pagination-links.json
object
Represents pagination links for navigating between pages of data.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cvent-event-cloud-event-features-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 Event Features 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.