Cvent Event Cloud Card Tokens API
**Card Tokenization**: Tokenization is the process Cvent uses to collect sensitive card details andpersonally identifiable information (PII), directly from your customers in a secure manner.This guarantees that no sensitive card data touches your server, and allows your integration tooperate in compliance with PCI standards. A card token is a unique identifier that represents sensitive credit card information.It is used as a secure alternative to directly handling credit card details during transactions.The token can be used in place of the actual credit card data when making API calls, providing an extra layer of security.
Cvent Event Cloud Card Tokens 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 Card Tokens. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Cvent Event Cloud Card Tokens 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 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Card Tokenization: Tokenization is the process Cvent uses to collect sensitive card details and personally identifiable information (PII), directly from your customers in a secure…
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are credit-card.json (17 properties), ErrorResponseBase (3 properties), cardTokenResponse (2 properties), cardTokenRequest (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Cvent Event Cloud 12
Other APIs Cvent Event Cloud publishes across the network.
This is an independent, third-party profile of Cvent Event Cloud Card Tokens 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.