openapi: 3.2.0
info:
title: Cvent REST APIs — Event Cloud Sessions API
description: "Event Cloud scope of the Cvent REST APIs. This document is a TAG-SCOPED SUBSET of the OpenAPI specification Cvent publishes at https://github.com/cvent/rest-sdks/blob/main/cvent-public-spec/openapi.yaml (the source of truth for Cvent's official TypeScript/.NET/Java SDKs). Venue-sourcing, RFP, housing-supplier and travel-supplier tags were removed because they belong to Cvent Hospitality Cloud; every path, operation, parameter, schema and security requirement below is verbatim from Cvent's published spec.\n\n# Introduction\nThe Cvent API Platform is built around REST. We aim to provide intuitive endpoints that can be easily\ndiscovered to help leverage the Cvent platform for your event needs. The RESTful APIs outlined here\nuse JSON-encoded request and response format, along with HTTP codes, to convey processing status of\nrequests received. The Cvent resources are protected using OAuth2.\n\n# Getting Started\n\nIf you're new to the Cvent API Platform, start by reading our\n[Developer Quickstart](https://developers.cvent.com/docs/rest-api/tutorials/developer-quickstart) guide. This will\ngive you an overview of how to authenticate and make requests using our APIs.\n\n## Authentication\n\nThe Cvent REST API uses [OAuth2](https://oauth.net/2/) to authorize requests to the platform. The client\ncredentials authorization flow is supported.\n\n<a name=\"oauth2-auth-code-planner-admin\"></a>\n\nAuthorization code flow is only supported for planner users with the administrator role in Cvent. Developer users\ncannot use authorization code flow.\n\n<!-- ReDoc-Inject: <security-definitions> -->\n\nHere's an example of using client credential flow to authorize. You'll supply your application's id and secret to\nmake a [Token](#operation/oauth2Token) request.\n\n```bash\ncurl --location --request POST '{hostName}/{version}/oauth2/token' \\\n--header 'Content-Type: application/x-www-form-urlencoded' \\\n--header 'Authorization: Basic {api_credentials}' \\\n--data-urlencode 'grant_type=client_credentials' \\\n--data-urlencode 'client_id={client_id}'\n```\n\n| Key | Description | Value |\n| :---------------- | :--------------------------------------------------- | :----------------------------------------------------------------------------------------------------------- |\n| {hostName} | https://api-platform.cvent.com | Location if your account is in the North American datacenter. |\n| | https://api-platform-eur.cvent.com | Location if your account is in the European data center. |\n| {version} | ea | The version of the API you're using. Only `ea` is currently supported. |\n| {api_credentials} | {client_id}:{client_secret} in base64 encoded format | Supply your client id & client credentials in a base 64 encoded format. |\n| {client_id} | Retrieved from your application | Your application's client id. |\n| {client_secret} | Retrieved from your application | Your application's client secret. |\n\nOn a successful call, you'll receive the following response:\n\n```json\n{\n \"access_token\": \"{accessToken}\",\n \"expires_in\": 3600,\n \"token_type\": \"Bearer\"\n}\n```\n\nThis bearer token is valid for 3600 seconds (60 minutes) and must be used in subsequent calls.\n\n## Endpoints\n\nEndpoints start with `hostName` and `version`.\n\nThe `hostname` will depend on the region that your Cvent account is hosted in. Please see the table\nbelow to identify which hostname you should be using.\n\n| Region |\tHostname |\n|:--------------|:-----------------------------------|\n| North America\t| https://api-platform.cvent.com |\n| Europe | https://api-platform-eur.cvent.com |\n\nThe current `version` of the Cvent API is `ea`.\n\n## Rate Limits\n\nCvent APIs enforce rate limits to ensure platform stability. Your limits depend on your tier: Free,\nStandard, or Premium.\n\n<br />\n\n### Usage Tiers\n\n| Tier | Daily Calls | Calls per Second | Max Burst |\n| -------- | ----------- | ---------------- | --------- |\n| Free | 1,000 | 2 | 1 |\n| Standard | 15,000 | 10 | 10 |\n| Premium | 500,000 | 25 | 25 |\n\n- **Daily calls** define how many requests you can make in a 24-hour period. Quota\n resets at 12 midnight (+0 GMT).\n- **Calls per second** define how many requests you can make in a 1-second window.\n- **Max Burst** defines how many requests you can make at once.\n\nIf you are unsure what usage tier applies to your account, you can check via\n[Get Current Usage Tier](#operation/getUsageTier).\n\nPlease note that these limits may change as the Cvent API Platform evolves.\n\n<br />\n\n### Handling Rate Limits\n\nSometimes, you may exceed your rate limits. When this happens, the API will return a `429 Too Many Requests`. See\n[handling rate limits](https://developers.cvent.com/docs/rest-api/guides/handling-rate-limits) for best practices on how to handle this.\n\n## Pagination\n\nSome APIs use pagination to manage records. Each page of records has a token associated to identify it.\n\nIf an API uses pagination, you’ll find up to three tokens in the response:\n- **currentToken**: Describes the token of the current page.\n- **nextToken**: Provides a token for the next page of records, if one exists.\n- **previousToken**: Provides a token for the previous page of records, if one exists. Not all APIs will return\n this token.\n\nYou specify which page of records to view via the `token` parameter in your API call. To navigate through pages,\ntake the `nextToken` or `previousToken` value and pass it to your next call’s `token` parameter to get the\nrespective page of records. For example, if you made this request:\n\n```bash\ncurl -X GET {hostname}/{version}/contacts?limit=100 \\\n-H 'Accept: application/json' \\\n-H 'Authorization: Bearer {accessToken}'\n```\n\nThe response contains a paging array where you'll find the token information.\n\n```json\n{\n \"paging\": {\n \"currentToken\": \"90c5f062-76ad-4ea4-aa53-00eb698d9262\",\n \"nextToken\": \"3b2359a7-4583-40ed-8afd-67e5f15373d3\",\n \"limit\": 100,\n \"totalCount\": 102,\n \"_links\": {...}\n },\n \"data\": [...]\n}\n```\n\nTake the `nextToken` and use it in the `token` parameter on your subsequent call.\n\n```bash\ncurl -X GET {hostname}/{version}/contacts?limit=100&token=3b2359a7-4583-40ed-8afd-67e5f15373d3 \\\n-H 'Accept: application/json' \\\n-H 'Authorization: Bearer {accessToken}'\n```\n\nWhen the response doesn’t contain a `nextToken` field, you’ve reached the last page. Occasionally, you might\nencounter an empty page at the end of results. This typically happens when the results were evenly divisible.\nEnsure your client code handles the possibility of receiving an empty data array when using the `nextToken`.\n\n## Filtering\n\nUse filters to narrow down results. The filter follows the pattern\n`filter='field' comparisonType 'value'`. The value can be enclosed with single\nquotes (') or double quotes (\").\n\n```bash\nGET {hostName}/{version}/contacts?filter=lastName eq 'Smith'\n````\n\nTo correctly pass a single quote in the filter's value, use double quotes around\nthe string.\n\n```bash\nGET {hostName}/{version}/contacts?filter=lastName eq \"O'Keenan\"\n```\n\nTo correctly pass a double quote in the filter's value, use double quotes around\nthe string and add an escape character `\\` to each quote that is part of the\nstring.\n\n```bash\nGET {hostName}/{version}/events?filter=eventName eq \"\\\"Yearly\\\" Conference\"\n```\n\n## Versioning\n\nChange is inevitable in API development. Planning for it is crucial. We track\nboth backward-compatible and backward-incompatible changes.\n\n<br />\n\n### Backward Compatible Changes\n\nBackward compatible changes will be made often and are intended to avoid\nany adverse impact on our customers. It is highly advisable that when reading\nJSON payloads from Cvent, you are able to handle \"unknown\" attributes that\ncan be added over time. We consider the following changes backward-compatible:\n\n- Adding new resources\n- Adding new optional request parameters to existing operations\n- Adding new attributes to requests or responses\n- Changing the length or format (not type) of resource identifiers. For example, an ID can change from\n \"1234/1234\" to \"1234::1234\".\n- Increasing the length of string fields\n\n<br />\n\n### Backward Incompatible Changes\n\nBackward-incompatible changes are made infrequently, however, they can be\ndisruptive to consumers. Due to this, our APIs are versioned to avoid\ndisruptions to customers. We leverage a URI-based versioning scheme,\nwhich means that a version value is included in the Cvent API URL.\nWhen breaking changes occur, a new version of the API is made available\nwhile the existing version is deprecated but remains available for a\nlimited period of time. We consider the following backward-incompatible changes:\n\n- Adding a new required parameter (query string param or payload attribute)\n- Deleting API resources\n- Deleting any attribute from API responses\n- Changing the data type on any parameter or attribute\n\n## Standards\nAs you begin working with our APIs, it's essential to be aware of standards around\ncountry codes, time formats, and other important details that ensure smooth integration.\nLearn more about our [API Standards](https://developers.cvent.com/docs/rest-api/reference/api-standards)\n"
contact:
name: Cvent Development Platform
url: https://developers.cvent.com/
version: ea
servers:
- url: https://api-platform.cvent.com/ea
- url: https://api-platform-eur.cvent.com/ea
tags:
- name: Sessions
description: A session is a presentation, discussion, or activity. Use these APIs to get information about your sessions and use the session ID to get further data within the event.
paths:
/events/{id}/session-locations:
parameters:
- $ref: '#/components/parameters/eventId1'
get:
security:
- OAuth2.clientCredentials:
- event/sessions:read
- OAuth2.authorizationCode:
- event/sessions:read
summary: List Session Locations
description: Gets a paginated list of session locations.
operationId: getSessionLocation
tags:
- Sessions
parameters:
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
responses:
'200':
description: Successfully retrieved paginated list of session locations.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/session-locations-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
post:
security:
- OAuth2.clientCredentials:
- event/sessions:write
- OAuth2.authorizationCode:
- event/sessions:write
summary: Add Session Location
description: Add a session location to the specified event.
operationId: addSessionLocation
tags:
- Sessions
requestBody:
description: Details of the session location you're creating.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/session-location'
responses:
'201':
description: Successfully created a session location
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/session-location'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/program-items:
post:
security:
- OAuth2.clientCredentials:
- event/program-items:write
- OAuth2.authorizationCode:
- event/program-items:write
summary: Create Program Item
description: Create a session program item based on the details provided in the body of the request. A session program item is a specific part of a session's schedule, like a talk, workshop, or panel discussion. Max 25 program items per session.
operationId: createProgramItem
tags:
- Sessions
requestBody:
description: Session program item to be created.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/program-item'
responses:
'201':
description: Successfully created the session program item.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
get:
security:
- OAuth2.clientCredentials:
- event/program-items:read
- OAuth2.authorizationCode:
- event/program-items:read
summary: List Program Items
description: Gets a paginated list of session program items.
operationId: listProgramItems
tags:
- Sessions
parameters:
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
- name: filter
in: query
required: false
description: 'Use filter query parameters to limit results
to data that matches your criteria. See
[Filters](https://developers.cvent.com/docs/rest-api/reference/filters) for details.
Supported fields and operators are listed below:
| Field | Operators |
|------------|------------|
| id | `eq`, `in` |
| session.id | `eq`, `in` |
| event.id | `eq` |
The following logical operators are supported for combining filters:
* and
* or
'
schema:
type: string
example: session.id in ('04ca6ae2-0dc3-487b-953e-86d6abbdf7d3', '34ca65e2-1dc3-487b-589e-839d8bbdf7d3')
responses:
'200':
description: Successfully retrieved a paginated list of session program items.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/program-items/docs/filter:
post:
security:
- OAuth2.clientCredentials:
- event/program-items:read
- OAuth2.authorizationCode:
- event/program-items:read
summary: Filter Program Item Documents
description: Gets a paginated list of session program item documents using a filter in the body of the request.
operationId: filterProgramItemDocuments
tags:
- Sessions
requestBody:
description: "A filter query string narrows search results and supports the combination of logical and comparison operators.\nThe filter adheres to the pattern filter='field' comparisonType 'value'.\n\nThese are the comparison types that can be used in filter expressions:\n * equal: eq\n * includes value(s): in\n\nThe following fields are filterable:\n * document.id (eq|in)\n * programItem.id (eq|in)\n * session.id (eq|in)\n * event.id (eq)\n\nThe following operators are available:\n * and\n * or\n"
required: false
content:
application/json:
schema:
$ref: '#/components/schemas/filter'
parameters:
- $ref: '#/components/parameters/after'
- $ref: '#/components/parameters/before'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
responses:
'200':
description: Successfully retrieved a paginated list of session program item documents.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-document-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/program-items/filter:
post:
security:
- OAuth2.clientCredentials:
- event/program-items:read
- OAuth2.authorizationCode:
- event/program-items:read
summary: List Program Items
description: Gets a paginated list of session program items by sending a filter in the body of the request. This method will return the same data as <a href="#operation/listProgramItems">GET List Program Items</a> but allows for longer filters.
operationId: listProgramItemsPostFilters
tags:
- Sessions
requestBody:
description: See the filter description of <a href="#operation/listProgramItems">GET List Program Items</a> for full filtering information.
required: false
content:
application/json:
schema:
$ref: '#/components/schemas/filter'
parameters:
- $ref: '#/components/parameters/after'
- $ref: '#/components/parameters/before'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
- $ref: '#/components/parameters/locale1'
responses:
'200':
description: Successfully retrieved a paginated list of session program items.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/program-items/{programItemId}:
parameters:
- $ref: '#/components/parameters/programItemId1'
put:
security:
- OAuth2.clientCredentials:
- event/program-items:write
- OAuth2.authorizationCode:
- event/program-items:write
summary: Update Program Item
description: Updates the given session program item based on the details provided in the body of the request.
operationId: updateProgramItem
tags:
- Sessions
requestBody:
description: Session program item to be updated.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-update-request'
responses:
'200':
description: Successfully updated the session program item.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
delete:
security:
- OAuth2.clientCredentials:
- event/program-items:delete
- OAuth2.authorizationCode:
- event/program-items:delete
summary: Delete Session Program Item
description: Delete the given session program item.
operationId: deleteProgramItem
tags:
- Sessions
responses:
'204':
description: Successfully deleted the given session program item.
headers: {}
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/program-items/{programItemId}/docs:
parameters:
- $ref: '#/components/parameters/programItemId1'
get:
security:
- OAuth2.clientCredentials:
- event/program-items:read
- OAuth2.authorizationCode:
- event/program-items:read
summary: Get Program Item Documents
description: 'Returns a list of session documents for the specified program item ID.
**Note:** This endpoint is deprecated. use <a href="#operation/filterProgramItemDocuments">Filter Program Item Documents</a>'
operationId: getProgramItemDocuments
tags:
- Sessions
responses:
'200':
description: Successfully retrieved a list of program item to session document relationships for the specified program item ID.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-session-documents'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
deprecated: true
/program-items/{programItemId}/docs/{fileId}:
parameters:
- $ref: '#/components/parameters/programItemId1'
- $ref: '#/components/parameters/fileId'
put:
security:
- OAuth2.clientCredentials:
- event/program-items:write
- OAuth2.authorizationCode:
- event/program-items:write
summary: Add Program Item Document
description: Creates a relationship between a session program item and a session document. Limit 10 session documents per session program item.
operationId: relateProgramItemToSessionDocument
tags:
- Sessions
responses:
'200':
description: Successfully created the relationship between the session program item and the session document.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-session-document'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'409':
description: Program item session document limit reached.
content:
application/json:
schema:
$ref: '#/components/schemas/baseErrorResponse'
example:
code: 409
message: Conflict
'429':
$ref: '#/components/responses/TooManyRequests1'
get:
security:
- OAuth2.clientCredentials:
- event/program-items:read
- OAuth2.authorizationCode:
- event/program-items:read
summary: Get Program Item Document
description: Returns a single program item to session document relationship for the provided IDs.
operationId: getProgramItemSessionDocument
tags:
- Sessions
responses:
'200':
description: Successfully retrieved a program item to session document relationship for the provided IDs.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/program-item-session-document'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
delete:
security:
- OAuth2.clientCredentials:
- event/program-items:delete
- OAuth2.authorizationCode:
- event/program-items:delete
summary: Delete Program Item Document
description: Deletes session program item to session document relationship based on the provided IDs.
operationId: deleteProgramItemSessionDocument
tags:
- Sessions
responses:
'204':
description: Successfully deleted session program item to session document relationship.
headers: {}
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/session-categories:
get:
security:
- OAuth2.clientCredentials:
- event/session-categories:read
- OAuth2.authorizationCode:
- event/session-categories:read
summary: List Session Categories
description: Gets a paginated list of session categories.
operationId: listSessionsCategories
parameters:
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
- name: sort
in: query
required: false
style: form
explode: false
description: "The sort order passed as a parameter, used to control the order of the\nsearch results as a priority ordered list of sorts\n\nThere are two orders:\n * ascending: ASC\n * descending: DESC\n\nThe following fields are sortable:\n * name\n"
schema:
type: string
example: name:ASC
- name: filter
in: query
required: false
description: "Use filter query parameters to limit results\nto data that matches your criteria. See\n[Filters](https://developers.cvent.com/docs/rest-api/reference/filters) for details.\n\nSupported fields and operators are listed below:\n\n| Field | Operators |\n|------------------|-------------------------------------|\n| id | `eq`, `ne`, `in` |\n| name | `eq`, `ne`, `contains` |\n\nThe following operators are available:\n * and\n * or\n"
schema:
type: string
example: name contains 'general'
tags:
- Sessions
responses:
'200':
description: Successfully retrieved a paginated list of sessions categories.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/session-category-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
deprecated: false
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
post:
security:
- OAuth2.clientCredentials:
- event/session-categories:write
- OAuth2.authorizationCode:
- event/session-categories:write
summary: Create Session Categories
description: Create a session category.
operationId: createSessionCategory
tags:
- Sessions
requestBody:
description: Contains the details of the session category you're creating.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/session-category'
responses:
'201':
description: Successfully created a session category.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/session-category'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
deprecated: false
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/session-segments:
get:
security:
- OAuth2.clientCredentials:
- event/session-segments:read
- OAuth2.authorizationCode:
- event/session-segments:read
summary: Get Session Segments
description: Return a list of session and audience segment associations.
operationId: GetSessionSegments
tags:
- Sessions
parameters:
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
- name: filter
in: query
required: false
description: "A filter query string narrows search results and supports the combination of logical and comparison operators.\nThe filter adheres to the pattern filter='field' comparisonType 'value'.\n\nThere are two comparison types that can be used in filter expressions:\n * equal: eq\n * includes value(s): in\n\nThe following field is filterable:\n * segment.id (eq|in)\n * session.id (eq|in)\n\nThe following operators are available:\n * and\n * or\n"
schema:
type: string
example: segment.id in ('04ca6ae2-0dc3-487b-953e-86d6abbdf7d3', '34ca65e2-1dc3-487b-589e-839d8bbdf7d3')
responses:
'200':
description: Successfully retrieved a paginated list of session and audience segment associations.
headers: {}
content:
application/json:
schema:
$ref: '#/components/schemas/session-segment-paginated-response'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/sessions:
get:
security:
- OAuth2.clientCredentials:
- event/sessions:read
- OAuth2.authorizationCode:
- event/sessions:read
summary: List Sessions
description: Gets a paginated list of sessions.
operationId: listSessions
parameters:
- $ref: '#/components/parameters/after'
- $ref: '#/components/parameters/before'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token'
- $ref: '#/components/parameters/sort6'
- $ref: '#/components/parameters/locale1'
- name: filter
in: query
required: false
descript
# --- truncated at 32 KB (127 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-sessions-api-openapi.yml