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

Operations for managing account users and user groups, including creation, retrieval, update, and deletion. Use these endpoints to administer user access and roles within your account.

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

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

7 operations 3 paths 8 schemas 2 DELETE2 GET2 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 Users 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 7

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

Users 7

Operations for managing account users and user groups, including creation, retrieval, update, and deletion. Use these endpoints to administer user access and roles within your acc…

GET
/account-user-groups
List Account User Groups
getAccountUserGroups 3 params → 200400401403429
POST
/account-user-groups
Create Account User Group
createAccountUserGroup body → 200400401403429
GET
/account-user-groups/{userGroupId}
Get Account User Group
getAccountUserGroup 1 param → 200400401403404429
PUT
/account-user-groups/{userGroupId}
Update Account User Group
updateAccountUserGroup 1 param body → 200400401403404429
DELETE
/account-user-groups/{userGroupId}
Delete Account User Group
deleteAccountUserGroup 1 param → 204400401403404429
POST
/account-user-groups/{userGroupId}/users/{userId}
Associate User to Group
addUserToAccountUserGroup 2 params → 204400401403404429
DELETE
/account-user-groups/{userGroupId}/users/{userId}
Delete User from Group
deleteUserFromAccountUserGroup 2 params → 204400401403404429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Account (9 properties), paging.json (6 properties), ErrorResponseBase (3 properties), user-group.json (3 properties). Each schema is shown below with its type and property counts.

link.json
object
Represents a link to a related resource.
1 property 1 required
user-groups.json
object
A paginated result for a list of user groups.
2 properties 2 required
ErrorResponse
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
Account
object
The definition of a Cvent Core Account. This is the primary entity a Cvent User interacts. Once logged into the Cvent platform, the User can interact with the…
9 properties 7 required
user-group.json
object
A collection of account users which is used to help manage access and visibility to various other Cvent domain entities like events, surveys, account emails, a…
3 properties 6 required
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
ErrorResponseBase
object
Represents an error response with no additional details.
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-users-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 Users 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.