openapi: 3.2.0
info:
title: Cvent REST APIs — Event Cloud Users 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: Users
description: Operations for managing account users and user groups, including creation, retrieval, update, and deletion. Use these endpoints to administer user access and roles within your account.
paths:
/account-user-groups:
get:
summary: List Account User Groups
description: Gets a list of user groups in your account.
operationId: getAccountUserGroups
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:read
- OAuth2.clientCredentials:
- account/user-groups:read
parameters:
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/token1'
- name: filter
in: query
required: false
style: form
explode: true
description: 'Filters narrow the results returned and support a combination of logical and comparison operators. The filter adheres to the pattern filter=''field'' comparisonType ''value''. The following logical operators and fields are supported:
| Field Path | Operators |
|-----------------|------------------------------------|
| name | `in`, `eq`, `ne`, `sw`, `ew`, `co` |
| createdBy | `in`, `eq`, `ne`, `sw`, `ew`, `co` |
| lastModifiedBy | `in`, `eq`, `ne`, `sw`, `ew`, `co` |
| created | `eq`, `ne`, `lt`, `gt`, `le`, `ge` |
| lastModified | `eq`, `ne`, `lt`, `gt`, `le`, `ge` |
'
schema:
type: string
example: name eq 'My User Group'
responses:
'200':
$ref: '#/components/responses/UserGroups'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
post:
summary: Create Account User Group
operationId: createAccountUserGroup
description: 'Creates a new Account User Group.
'
tags:
- Users
parameters: []
security:
- OAuth2.authorizationCode:
- account/user-groups:write
- OAuth2.clientCredentials:
- account/user-groups:write
requestBody:
$ref: '#/components/requestBodies/UserGroup'
responses:
'200':
$ref: '#/components/responses/UserGroup'
'400':
$ref: '#/components/responses/BadRequest1'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/account-user-groups/{userGroupId}:
get:
summary: Get Account User Group
description: Gets a single account user group by its ID.
operationId: getAccountUserGroup
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:read
- OAuth2.clientCredentials:
- account/user-groups:read
parameters:
- $ref: '#/components/parameters/userGroupId'
responses:
'200':
$ref: '#/components/responses/UserGroup'
'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'
put:
summary: Update Account User Group
description: Update a given account user group using details in the body of the request.
operationId: updateAccountUserGroup
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:write
- OAuth2.clientCredentials:
- account/user-groups:write
parameters:
- $ref: '#/components/parameters/userGroupId'
requestBody:
$ref: '#/components/requestBodies/UserGroup'
responses:
'200':
$ref: '#/components/responses/UserGroup'
'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:
summary: Delete Account User Group
description: Deletes an account user group using its ID.
operationId: deleteAccountUserGroup
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:delete
- OAuth2.clientCredentials:
- account/user-groups:delete
parameters:
- $ref: '#/components/parameters/userGroupId'
responses:
'204':
description: 'No content, the group has been deleted.
'
'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'
/account-user-groups/{userGroupId}/users/{userId}:
post:
summary: Associate User to Group
description: Associates a user to an account user group.
operationId: addUserToAccountUserGroup
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:write
- OAuth2.clientCredentials:
- account/user-groups:write
parameters:
- $ref: '#/components/parameters/userGroupId'
- $ref: '#/components/parameters/userId'
responses:
'204':
description: 'No content, the user has been added to the group.
'
'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:
summary: Delete User from Group
description: Removes a user from an account user group.
operationId: deleteUserFromAccountUserGroup
tags:
- Users
security:
- OAuth2.authorizationCode:
- account/user-groups:delete
- OAuth2.clientCredentials:
- account/user-groups:delete
parameters:
- $ref: '#/components/parameters/userGroupId'
- $ref: '#/components/parameters/userId'
responses:
'204':
description: 'No content, the user has been removed from the group.
'
'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'
components:
responses:
TooManyRequests1:
description: Too many requests
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
code: 429
message: Limit Exceeded
NotFound1:
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
code: 404
message: Not found
Unauthorized1:
description: Bad or expired token
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
code: 401
message: Unauthorized
Forbidden1:
description: You do not have access to the resource
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
code: 403
message: Access Forbidden
BadRequest1:
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
code: 400
message: Bad Request
UserGroups:
description: List of User Groups
content:
application/json:
schema:
$ref: '#/components/schemas/user-groups.json'
UserGroup:
description: A User Group
content:
application/json:
schema:
$ref: '#/components/schemas/user-group.json'
schemas:
Account:
title: Account
description: The definition of a Cvent Core Account. This is the primary entity a Cvent User interacts. Once logged into the Cvent platform, the User can interact with the different product lines the account is allotted to.
required:
- id
- tinyId
- number
- stub
- activated
- inactivated
- audit
type: object
allOf:
- title: Account Base
description: The base definition of a Cvent Core Account.
required:
- status
- type
- name
- company
- url
- showCreditCardWarning
- creditCardEntryDeadline
type: object
properties:
customer:
$ref: '#/components/schemas/customer-reference.json'
name:
type: string
description: The name of the Account.
example: Cvent
company:
type: string
description: The Account's company name.
example: Cvent
url:
type: string
format: uri
description: A url which points to the Account's company website.
example: https://www.cvent.com
status:
$ref: '#/components/schemas/account-status.json'
type:
$ref: '#/components/schemas/account-type.json'
showCreditCardWarning:
type: boolean
description: True means to show the credit card warning for the Account.
creditCardEntryDeadline:
type: string
format: date-time
description: The ISO 8601 zoned date time of the Account's credit card entry deadline.
example: '2019-07-15T09:00:39Z'
properties:
organization:
type: object
allOf:
- title: Organization Reference
description: A model used to reference the identifier to a Cvent Organization.
required:
- id
- number
- stub
type: object
properties:
id:
$ref: '#/components/schemas/organization-id.json'
stub:
$ref: '#/components/schemas/Organization1/properties/stub/allOf/0'
number:
$ref: '#/components/schemas/organization-number.json'
- readOnly: true
id:
$ref: '#/components/schemas/account-id.json'
tinyId:
type: string
description: The Account's shortened alphanumeric identifier.
example: vnzb
readOnly: true
number:
$ref: '#/components/schemas/account-number.json'
stub:
$ref: '#/components/schemas/account-stub.json'
administratorRole:
type: object
allOf:
- title: Account User Role Reference
description: A model used to reference a Cvent core account user role by its ID.
required:
- id
type: object
properties:
id:
$ref: '#/components/schemas/AccountUserRole/properties/id/allOf/1'
- readOnly: true
activated:
type: string
format: date-time
description: The ISO 8601 zoned date time when this Account has been activated.
readOnly: true
example: '2019-07-15T09:00:39Z'
inactivated:
type: string
format: date-time
description: The ISO 8601 zoned date time when this Account has been inactivated.
readOnly: true
example: '2019-07-15T09:00:39Z'
audit:
type: object
allOf:
- title: Audit
description: Audit information
type: object
properties:
created:
type: string
format: date-time
description: The ISO 8601 zoned date time when this record was created.
readOnly: true
example: '2017-01-02T02:00:00Z'
createdBy:
type: string
description: The identifier of the user that created this record.
readOnly: true
example: hporter
lastModified:
type: string
format: date-time
description: The ISO 8601 zoned date time when this record was updated.
readOnly: true
example: '2019-02-12T03:00:00Z'
lastModifiedBy:
type: string
description: The identifier of the user that last updated this record.
readOnly: true
example: hporter
- readOnly: true
paging.json:
title: Paging
required:
- _links
type: object
description: Represents pagination information for a collection of resources.
properties:
previousToken:
type: string
description: The pagination token for the previous page, if one exists. You can use this token to navigate to the previous page of data.
example: 1a2b3c4d5e6f7g8h9i10j11k
nextToken:
type: string
description: The pagination token for the next page. If this value is present in the response, there is another page of data you can fetch.
example: 1a2b3c4d5e6f7g8h9i10j11k
currentToken:
type: string
description: The pagination token for the current page.
example: 1a2b3c4d5e6f7g8h9i10j11k
limit:
type: integer
description: The number of records to return on the page. Not to exceed 200.
example: 100
totalCount:
type: integer
description: The total number of records available. This field may return blank, even if there are more records. To confirm if there are more records, check the `nextToken` field.
example: 2
_links:
$ref: '#/components/schemas/pagination-links.json'
link.json:
title: Link
required:
- href
type: object
description: Represents a link to a related resource.
properties:
href:
type: string
description: A url provided that can be followed for linking
example: ?token=90c5f062-76ad-4ea4-aa53-00eb698d9262
ErrorResponseBase:
title: ErrorResponseBase
type: object
description: Represents an error response with no additional details.
required:
- code
- message
properties:
code:
type: integer
description: The HTTP status code representing the error.
example: 400
message:
type: string
description: A brief description of the error.
example: Bad Request
target:
type: string
description: The target resource of the error.
example: example target
ErrorResponse:
title: ErrorResponse
description: Represents an error response with additional details of cascading error messages.
allOf:
- $ref: '#/components/schemas/ErrorResponseBase'
type: object
required:
- code
- message
properties:
details:
type: array
items:
$ref: '#/components/schemas/ErrorResponseBase'
description: Additional details of cascading error messages.
user-groups.json:
title: User Groups
description: A paginated result for a list of user groups.
required:
- paging
- data
type: object
properties:
paging:
$ref: '#/components/schemas/paging.json'
data:
type: array
items:
$ref: '#/components/schemas/user-group.json'
description: The list of user groups retrieved for the specified page.
readOnly: true
user-group.json:
title: Account User Group
description: A collection of account users which is used to help manage access and visibility to various other Cvent domain entities like events, surveys, account emails, and more. For example, a user group can be associated to specific events to allow the users within that group to view the events within Cvent's platform.
required:
- id
- name
- created
- createdBy
- lastModified
- lastModifiedBy
type: object
allOf:
- $ref: '#/components/schemas/Account/properties/audit/allOf/0'
properties:
id:
type: string
format: uuid
description: The unique identifier of the user group.
example: EBF2273A-35A5-BD67-A292-397539D13270
readOnly: true
name:
type: string
description: The name of the user group.
example: MyUserGroup
minLength: 1
maxLength: 50
description:
type: string
description: The description of the user group.
example: MyUserGroupDescription
maxLength: 300
pagination-links.json:
title: PaginationLinks
type: object
description: Represents pagination links for navigating between pages of data.
properties:
next:
$ref: '#/components/schemas/link.json'
self:
$ref: '#/components/schemas/link.json'
prev:
$ref: '#/components/schemas/link.json'
requestBodies:
UserGroup:
description: A User Group
content:
application/json:
schema:
$ref: '#/components/schemas/user-group.json'
parameters:
userGroupId:
in: path
name: userGroupId
description: 'The User Group''s Id.
'
required: true
schema:
type: string
format: uuid
example: B089AC31-1212-63FB-AAEA-382037E1BCDF
userId:
in: path
name: userId
description: 'The Account User''s Id.
'
required: true
schema:
type: string
format: uuid
example: FF8AF134-3505-4D67-AAEA-1975D8E1327C
limit:
name: limit
in: query
description: The maximum number of records to return per page.
style: form
explode: true
schema:
maximum: 200
minimum: 1
type: integer
default: 100
example: 100
token1:
in: query
name: token
description: 'The pagination token returned from a previous call.
This will override any other pageable parameters provided.
'
required: false
style: form
explode: true
schema:
type: string
example: 1a2b3c4d5e6f7g8h9i10j11k
securitySchemes:
OAuth2.authorizationCode:
type: oauth2
description: OAuth2 Authorization Code Flow.
flows:
authorizationCode:
authorizationUrl: https://api-platform.cvent.com/ea/oauth2/authorize
tokenUrl: https://api-platform.cvent.com/ea/oauth2/token
scopes:
account/hooks:delete: Allows the deletion of hooks.
account/hooks:read: Allows the reading of hooks.
account/hooks:write: Allows the creation/updation of hooks.
account/user-groups:delete: Allows deletion for user groups
account/user-groups:read: Allows the reading of user groups
account/user-groups:write: Allows the writing of user groups
account/users:delete: Allows the deletion of User
account/users:read: Allows the reading of User, User Group
account/users:write: Allows the creation/updating of User
appointments/appointment-attendees:read: Allows the reading of appointment attendees and their related entities.
appointments/appointment-events:read: Allows the reading of appointment events and their related entities.
appointments/appointment-types:read: Allows the reading of appointment types and their related entities.
appointments/appointments:read: Allows the reading of appointment and their related entities.
appointments/appointments:write: Allows the writing of appointments and their related entities.
appointments/available-times:read: Allows the reading of available times.
appointments/locations:read: Allows the reading of appointment locations and their related entities.
attendee-insights/attendee-insights:read: Allows the reading of engagement scores (attendee insights).
attendee-insights/scores:read: Allows the reading of scores.
attendee-insights/stats:read: Allows the reading of engagement score (attendee insight) stats.
budget/budget-items:delete: Allows the deletion of budget items
budget/budget-items:read: Allows the reading of all budget items
budget/budget-items:write: Allows creation/updation of budget item
budget/budget-totals:read: Allows the reading of all event budget totals
budget/budget-vendors:read: Allows reading of account-level budget vendors.
budget/cards:read: Allows the reading of cards
budget/currency-conversion-rate:delete: Allows deletion of currency conversion rate for currency.
budget/currency-conversion-r
# --- truncated at 32 KB (67 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-users-api-openapi.yml