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 Travel Accounts API

The travel account, or corporation that represents the demand-side of travel RFPs.

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

This API exposes 4 operations across 4 paths, and defines 13 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 13 schemas 4 GET

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 Travel Accounts 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 — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Travel Accounts 4

The travel account, or corporation that represents the demand-side of travel RFPs.

GET
/travel-accounts
List Travel Accounts
ListTravelAccounts 5 params → 200400401403429
GET
/travel-accounts/supplier-accounts
List Supplier Accounts
ListSupplierAccounts 5 params → 200400401403429
GET
/travel-accounts/{travelAccountId}
Get Travel Account
getTravelAccount 1 param → 200400401403404429
GET
/travel-accounts/{travelAccountId}/supplier-accounts
Get Supplier Account
getSupplierAccount 1 param → 200400401403404429

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are Address7 (8 properties), travel-account-supplier-account (7 properties), Paging (6 properties), travel-account (5 properties). Each schema is shown below with its type and property counts.

travel-account-supplier-account-paginated-response
object
A paginated list of supplier travel accounts.
2 properties
travel-account-supplier-account
object
Details for the supplier travel account. These details are supplier specific and only visible for supply-side clients.
7 properties
travel-account-paginated-response
object
A paginated list of travel accounts.
2 properties
ErrorResponse
object
Represents an error response with additional details of cascading error messages.
1 property 2 required
TravelAccountType
string
Code representing the travel account type.
travel-account
object
Travel account details.
5 properties
Paging
object
Represents pagination information for a collection of resources.
6 properties 1 required
Address7
object
Address details.
8 properties
Link
object
Represents a link to a related resource.
1 property 1 required
Audit
object
Audit information
4 properties
ErrorResponseBase
object
Represents an error response with no additional details.
3 properties 2 required
ManagementLevelType1
string
The management level of the travel account. Defined by the supply-side.
PaginationLinks
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-travel-accounts-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 Travel Accounts 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.