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 Audience Segments API

Audience Segments allow planners to segment their attendees into groups andbetter manage the attendee experience based on their defined segments. AudienceSegments APIs will enable you to get, create, and update segment information.These APIs will also allow you to get and update attendees associated with anaudience segment.

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

This API exposes 12 operations across 7 paths, and defines 22 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.

12 operations 7 paths 22 schemas 3 DELETE4 GET3 POST2 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 Audience Segments 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 12

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

Audience Segments 12

Audience Segments allow planners to segment their attendees into groups and better manage the attendee experience based on their defined segments. Audience Segments APIs will enab…

GET
/attendees/{attendeeId}/audience-segments
List Associated Segments
listAttendeeAudienceSegments 4 params → 200400401403404429
DELETE
/attendees/{attendeeId}/audience-segments
Delete Attendee Associations
disassociateAttendeeFromAudienceSegments 1 param → 204401403404429
POST
/attendees/{attendeeId}/audience-segments/filter
List Associated Segments
listAssociatedAudienceSegments 3 params body → 200400401403404429
POST
/audience-segments
Create Audience Segment
createAudienceSegment body → 201400401403422429
GET
/audience-segments
List Audience Segments
listAudienceSegments 6 params → 200400401403429
POST
/audience-segments/filter
List Audience Segments
listAudienceSegmentsPostFilter 5 params body → 200400401403429
GET
/audience-segments/{audienceSegmentId}
Get Audience Segment
getAudienceSegmentById 1 param → 200400401403404429
PUT
/audience-segments/{audienceSegmentId}
Update Audience Segment
updateAudienceSegment 1 param body → 200400401403404422429
DELETE
/audience-segments/{audienceSegmentId}
Delete Audience Segment
deleteAudienceSegment 1 param → 204401403404429
GET
/audience-segments/{audienceSegmentId}/attendees
List Associated Attendees
listSegmentAssociatedAttendees 7 params → 200400401403404429
PUT
/audience-segments/{audienceSegmentId}/attendees/{attendeeId}
Associate Attendee to Segment
associateAttendeeToSegment 2 params → 204400401403404422429
DELETE
/audience-segments/{audienceSegmentId}/attendees/{attendeeId}
Disassociate Attendee
disassociateAttendeeFromAudienceSegment 2 params → 204401403404429

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are paging.json (6 properties), attendee-segment (4 properties), audience-segment-response (3 properties), audience-segment (3 properties). Each schema is shown below with its type and property counts.

filter
object
A filter which is sent through the body of the request.
1 property
segment.json
object
Segment details
1 property 1 required
link.json
object
Represents a link to a related resource.
1 property 1 required
segment-attendee-response.json
object
Represents the attendees that are associated/disassociated to/from a segment
3 properties
uuid-property
string
A string that has to be a format matching the industry standard uuid
ErrorResponse
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
attendee-segment
object
Represents an attendee segment. Attendee segments are assigned to events and provide the ability for planners to segment their attendees into groups and better…
4 properties 2 required
segments-error-response
object
Segments error response details.
1 property
event.json
object
ID of the event.
1 property 1 required
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
segment-attendees-associated-paginated-response
object
The response from a request to get the paginated list of attendees associated/disassociated to/from an audience segment.
2 properties 2 required
existing-audience-segment
object
Details of an audience segment.
3 properties
audience-segment-create
object
Represents a request to create an audience segment.
1 property
audience-segments-paginated-response
object
The response from a request to get the paginated list of audience segments for the event.
2 properties 2 required
audience-segment-creation-type.json
string
Creation type of the audience segment.
existing-audience-segment-creation-type.json
string
Creation type of the audience segment.
attendee-audience-segment-associations-paginated-response
object
The paginated response from a request to get the list of audience segments associated with an attendee.
2 properties 2 required
attendee-audience-segment-association.json
object
Represents an audience segment associated with an attendee.
1 property 1 required
audience-segment-response
object
Details of an audience segment.
3 properties
ErrorResponseBase
object
Represents an error response with no additional details.
3 properties 2 required
audience-segment
object
Represents an audience segment. Audience segments are assigned to events and provide the ability for planners to segment their attendees into groups and better…
3 properties 2 required
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-audience-segments-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 Authentication API
Cvent Event Cloud Badge Print Job API
Cvent Event Cloud Badge Printer Pools API
Where this information came from

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