Cvent Hospitality Cloud · Authentication Profile

Cvent Hospitality Cloud Authentication

Authentication

Cvent Hospitality Cloud secures its APIs with oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

CateringGroup BookingsHospitalityHospitality CloudHotelsHousingAuthenticationPasskeyReservationsRFPRoom BlocksSalesSourcingSupplier NetworkVenues
Methods: oauth2 Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

OAuth2.clientCredentials oauth2
· flows: clientCredentials
OAuth2.authorizationCode oauth2
· flows: authorizationCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-09-07'
method: searched
docs:
  - https://developers.cvent.com/docs/rest-api/reference/reference
  - https://developers.cvent.com/docs/rest-api/tutorials/developer-quickstart
  - https://developers.cvent.com/docs/rest-api/explanation/concepts
note: >-
  Read from the securitySchemes block of the contract Cvent publishes at
  https://developers.cvent.com/documentation and cross-checked against the developer portal. Every
  hospitality operation is OAuth 2.0 bearer-protected: 'Authorization: Bearer {accessToken}', tokens
  valid for 60 minutes, minted at https://api-platform.cvent.com/ea/oauth2/token. Machine-to-machine
  integrations use client credentials and the call is attributed to the application; web applications use
  the authorization code flow and the call is attributed to the authenticating Cvent administrator, who
  must be both an admin and a registered developer.
  Two additional schemes in the contract, CallbackApiKeyAuth and CallbackBasicAuth, are INBOUND — they
  describe how Cvent authenticates itself to a subscriber's webhook endpoint, not how a client
  authenticates to Cvent.
  The legacy SOAP API does NOT use OAuth: it exchanges credentials for a session ticket via its own Login
  call (see wsdl/cvent-hospitality-cloud-soap-v200611.yml).
token_lifetime: 60 minutes
scope_count: 238
source: openapi/cvent-hospitality-cloud-authentication-openapi.yml, openapi/cvent-hospitality-cloud-event-travel-openapi.yml,
  openapi/cvent-hospitality-cloud-housing-hotels-openapi.yml, openapi/cvent-hospitality-cloud-housing-openapi.yml,
  openapi/cvent-hospitality-cloud-meeting-requests-openapi.yml, openapi/cvent-hospitality-cloud-proposal-drafts-openapi.yml,
  openapi/cvent-hospitality-cloud-rfp-additional-details-openapi.yml, openapi/cvent-hospitality-cloud-rfp-management-openapi.yml,
  openapi/cvent-hospitality-cloud-rfp-requirements-openapi.yml, openapi/cvent-hospitality-cloud-rfp-suppliers-openapi.yml,
  openapi/cvent-hospitality-cloud-signatures-openapi.yml, openapi/cvent-hospitality-cloud-travel-accounts-openapi.yml
  ...
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: OAuth2.clientCredentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-platform.cvent.com/ea/oauth2/token
    scopes: 238
  description: OAuth2 Client Credentials Flow.
  sources:
  - openapi/cvent-hospitality-cloud-authentication-openapi.yml
  - openapi/cvent-hospitality-cloud-event-travel-openapi.yml
  - openapi/cvent-hospitality-cloud-housing-hotels-openapi.yml
  - openapi/cvent-hospitality-cloud-housing-openapi.yml
  - openapi/cvent-hospitality-cloud-meeting-requests-openapi.yml
  - openapi/cvent-hospitality-cloud-proposal-drafts-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-additional-details-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-management-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-requirements-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-suppliers-openapi.yml
  - openapi/cvent-hospitality-cloud-signatures-openapi.yml
  - openapi/cvent-hospitality-cloud-travel-accounts-openapi.yml
  - openapi/cvent-hospitality-cloud-travel-rfps-openapi.yml
  - openapi/cvent-hospitality-cloud-travel-suppliers-openapi.yml
  - openapi/cvent-hospitality-cloud-venue-meeting-rooms-openapi.yml
  - openapi/cvent-hospitality-cloud-venue-profiles-openapi.yml
- name: OAuth2.authorizationCode
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api-platform.cvent.com/ea/oauth2/authorize
    tokenUrl: https://api-platform.cvent.com/ea/oauth2/token
    scopes: 208
  description: OAuth2 Authorization Code Flow.
  sources:
  - openapi/cvent-hospitality-cloud-authentication-openapi.yml
  - openapi/cvent-hospitality-cloud-event-travel-openapi.yml
  - openapi/cvent-hospitality-cloud-meeting-requests-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-additional-details-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-management-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-requirements-openapi.yml
  - openapi/cvent-hospitality-cloud-rfp-suppliers-openapi.yml
  - openapi/cvent-hospitality-cloud-signatures-openapi.yml
  - openapi/cvent-hospitality-cloud-travel-rfps-openapi.yml
  - openapi/cvent-hospitality-cloud-venue-meeting-rooms-openapi.yml
  - openapi/cvent-hospitality-cloud-venue-profiles-openapi.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/cvent-hospitality-cloud-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.