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

Capabilities Sessions API

The Sessions API from Capabilities — 2 operation(s) for sessions.

This API exposes 2 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api-platform-eur.cvent.com/ea, https://api-platform.cvent.com/ea.

2 operations 2 paths 10 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Servers
https://api-platform-eur.cvent.com/ea
https://api-platform.cvent.com/ea
Authentication
OAuth 2.0, OAuth 2.0, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 4

Capabilities Sessions API declares 4 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2.authorizationCode) using the authorizationCode flow, exposing 177 scopes. It supports OAuth 2.0 (OAuth2.clientCredentials) using the clientCredentials flow, exposing 206 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 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Sessions 2
GET
/events/{id}/session-locations
List Session Locations
getSessionLocation 2 params → 200400401403404429
GET
/sessions/{id}/speakers
List Session's Speakers
listSessionSpeakers 2 params → 200400401403404429

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are paging.json (6 properties), session-speaker.json (4 properties), pagination-links.json (3 properties), session-location (3 properties). Each schema is shown below with its type and property counts.

session-location
object
Used to denote a sessions location.
3 properties 2 required
paging.json
object
Represents pagination information for a collection of resources.
6 properties 1 required
session-locations-paginated-response
object
A paginated response of session locations.
2 properties 2 required
link.json
object
Represents a link to a related resource.
1 property 1 required
pagination-links.json
object
Represents pagination links for navigating between pages of data.
3 properties
uuid-property
string
A string that has to be a format matching the industry standard uuid
session-speaker.json
object
A session speaker
4 properties
session-speaker-paginated-response
object
The response from a request to get the list of session speakers. This includes the paging object as well as the collection of session speakers.
2 properties 2 required
category-id-name.json
object
A defined speaker category.
2 properties 1 required
session-lite.json
object
The unique identifier of a session.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

capabilities-sessions-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Capabilities Sessions 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.