openapi: 3.2.0
info:
title: Cvent REST APIs — Event Cloud User SCIM 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: User SCIM
description: The [SCIM](https://www.simplecloud.info/) standard allows for easier cross-domain identity management. This API allows you to manage your account users and SCIM groups (representing Cvent user roles).
paths:
/scim/v2/Groups:
get:
summary: Get SCIM Groups
operationId: getUserGroups
description: Gets a paginated list of SCIM groups (representing Cvent user roles) in an account.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
responses:
'200':
$ref: '#/components/responses/UsersGroupsResponse'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'429':
$ref: '#/components/responses/TooManyRequests17'
parameters:
- $ref: '#/components/parameters/startIndex'
- $ref: '#/components/parameters/count1'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/ResourceTypes:
get:
summary: List Resource Types
operationId: getResourceTypes
description: Gets a list of resource types.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
responses:
'200':
$ref: '#/components/responses/ResourceTypes'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/ResourceTypes/{id}:
get:
summary: Get Resource Type
operationId: getResourceType
description: Gets the details of a single resource type.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
parameters:
- $ref: '#/components/parameters/resourceId'
responses:
'200':
description: Successfully retrieved a Resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ResourceType'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'404':
$ref: '#/components/responses/NotFound17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/Schemas:
get:
summary: List Schemas
operationId: getSchemas
description: Gets the paginated list of user schemas and its extension models representing the user and SCIM groups (representing Cvent user roles).
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
responses:
'200':
$ref: '#/components/responses/UsersSchemaResponse'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/Schemas/{id}:
get:
summary: Get Schema
operationId: getSchema
description: Gets the details of a user schema and its extension models representing the user and SCIM groups (representing Cvent user roles).
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
parameters:
- $ref: '#/components/parameters/schemaId'
responses:
'200':
description: Successfully retrieved a schema.
content:
application/json:
schema:
$ref: '#/components/schemas/UsersSchema'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'404':
$ref: '#/components/responses/NotFound17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/ServiceProviderConfig:
get:
summary: Get Service Provider Config
operationId: getServiceProviderConfig
description: Gets Cvent's configurations of SCIM.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
responses:
'200':
$ref: '#/components/responses/ServiceProviderConfig'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/Users:
post:
summary: Create User
operationId: createUser
description: Creates a new user. For account users, the email address will initially be unverified. To verify it, please click on the link provided in the email sent to your email address.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:write
- OAuth2.authorizationCode:
- account/users:write
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/User'
responses:
'201':
description: Successfully created a user.
content:
application/json:
schema:
$ref: '#/components/schemas/User'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'409':
$ref: '#/components/responses/Conflict10'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
get:
summary: List Users
operationId: listUsers
description: Gets a list of users.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
parameters:
- $ref: '#/components/parameters/startIndex'
- $ref: '#/components/parameters/count1'
- 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 |
|-------------------|------------------------------------|
| userName | `eq`, `ne` |
| groups.value | `eq`, `ne` |
| active | `eq`, `ne` |
| id | `eq`, `ne` |
| emails.value | `eq`, `ne` |
| meta.lastModified | `eq`, `ne`, `lt`, `le`, `gt`, `ge` |
| meta.created | `eq`, `ne`, `lt`, `le`, `gt`, `ge` |
The following logical operators are supported for combining filters:
* and
* or
'
schema:
type: string
example: userName eq 'john@example.com' or userName eq 'Matt@example.com'
responses:
'200':
description: Successfully retrieved a paginated list of Users.
content:
application/json:
schema:
$ref: '#/components/schemas/Users'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
/scim/v2/Users/{id}:
get:
summary: Get User
operationId: getUser
description: Gets the details of a single user.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:read
- OAuth2.authorizationCode:
- account/users:read
parameters:
- $ref: '#/components/parameters/userId1'
responses:
'200':
description: Successfully retrieved a user.
content:
application/json:
schema:
$ref: '#/components/schemas/User'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'404':
$ref: '#/components/responses/NotFound17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
put:
summary: Update User
operationId: updateUser
description: Updates a user. In case of an account user, if the email address field is updated then please verify the new email address using the link received in the verification email.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:write
- OAuth2.authorizationCode:
- account/users:write
parameters:
- $ref: '#/components/parameters/userId1'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/User'
responses:
'200':
description: Successfully updated a user.
content:
application/json:
schema:
$ref: '#/components/schemas/User'
'400':
$ref: '#/components/responses/BadRequest17'
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'404':
$ref: '#/components/responses/NotFound17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
delete:
summary: Delete User
operationId: deleteUser
description: Deletes a user.
tags:
- User SCIM
security:
- OAuth2.clientCredentials:
- account/users:delete
- OAuth2.authorizationCode:
- account/users:delete
parameters:
- $ref: '#/components/parameters/userId1'
responses:
'204':
description: Successfully deleted a User.
headers: {}
'401':
$ref: '#/components/responses/Unauthorized17'
'403':
$ref: '#/components/responses/Forbidden17'
'404':
$ref: '#/components/responses/NotFound17'
'429':
$ref: '#/components/responses/TooManyRequests17'
externalDocs:
description: More about OAuth2 authorization code support for administrators
url: '#oauth2-auth-code-planner-admin'
components:
schemas:
UniquenessType:
title: Uniqueness Type
description: This is used to denote the uniqueness type of the attribute.
enum:
- none
- server
- global
type: string
example: global
Attribute:
title: Attribute
description: Attribute
type: object
properties:
name:
type: string
description: The name of the attribute.
example: userName
type:
$ref: '#/components/schemas/AttributeDataType'
multiValued:
type: boolean
description: Indicates if the attribute is multivalued.
example: true
description:
type: string
description: The description of the attribute.
example: This Attribute describes the property
required:
type: boolean
description: True indicates the attribute is required.
example: true
caseExact:
type: boolean
description: True indicates the attribute is case sensitive.
example: false
mutability:
$ref: '#/components/schemas/Mutability'
canonicalValues:
type: array
description: The list of canonical values of the attribute.
items:
type: string
example: work
returned:
$ref: '#/components/schemas/ReturnedType'
uniqueness:
$ref: '#/components/schemas/UniquenessType'
referenceTypes:
type: array
description: This is used to denote the reference type of the attribute.
items:
$ref: '#/components/schemas/ReferenceType'
subAttributes:
type: array
description: A collection of sub-attributes. Has the same structure as this attribute object.
items:
$ref: '#/components/schemas/Attribute'
AuthenticationSchema:
title: Authentication Schema
description: Authentication Schema
type: object
properties:
name:
type: string
description: The name of the authentication.
example: OAuth Bearer Token
description:
type: string
description: The description of the authentication.
example: Authentication scheme using the OAuth Bearer Token Standard
specUri:
type: string
description: The location of the authentication specifications.
example: https://developers.cvent.com/documentation#section/Introduction
documentationUri:
type: string
description: The location of the API documentation.
example: https://developers.cvent.com/documentation#section/Introduction
type:
type: string
description: The type of the authentication.
example: oauthbearertoken
primary:
type: boolean
description: True indicates the authentication is primary.
example: true
PhoneType:
title: PhoneType
description: The type of the phone number.
enum:
- work
- home
- mobile
type: string
example: work
UsersSchemas:
title: Schemas
description: Schemas
type: object
properties:
schemas:
type: array
items:
type: string
example: urn:ietf:params:scim:api:messages:2.0:ListResponse
description: The collection of user schemas.
itemsPerPage:
type: integer
description: The number of schemas per page.
example: 50
startIndex:
type: integer
description: Starting index of the response.
example: 1
totalResults:
type: integer
description: The total count of schemas.
example: 5
Resources:
type: array
items:
$ref: '#/components/schemas/UsersSchema'
description: The collection of schema resources.
ServiceProviderConfig:
title: ServiceProviderConfigs
description: Service Provider Configs
type: object
properties:
schemas:
type: array
items:
type: string
example: urn:ietf:params:scim:api:messages:2.0:ListResponse
description: The list of schemas using this resource.
documentationUri:
type: string
format: uri
description: The location of the API documentation.
example: https://developers.cvent.com/documentation#section/Introduction
patch:
description: Config details for patch operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the patch operation is supported.
example: false
bulk:
description: Config details for bulk operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the bulk operation is supported.
example: false
maxOperations:
type: integer
description: An integer value specifying the maximum number of operations.
example: 1
maxPayloadSize:
type: integer
description: An integer value specifying the maximum payload size in bytes.
example: 1048576
filter:
description: Config details for filter operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the filteration is supported.
example: false
maxResults:
type: integer
description: The maximum number of results in the response.
example: 100
changePassword:
description: Config details for change password operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the password change is supported.
example: false
sort:
description: Config details for sort operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the sort operation is supported.
example: false
etag:
description: Config details for change e-tag operations.
type: object
properties:
supported:
type: boolean
description: Indicates if the entity tag operation is supported.
example: false
authenticationSchemes:
type: array
items:
$ref: '#/components/schemas/AuthenticationSchema'
description: The collection of authentication schemas.
meta:
$ref: '#/components/schemas/Meta'
ErrorScimType:
title: ErrorScimType
description: This is used to denote the scim type of the error.
enum:
- invalidFilter
- uniqueness
- invalidSyntax
- invalidValue
type: string
example: invalidSyntax
ReferenceType:
title: Reference Type
description: This is used to denote the reference type of the attribute.
enum:
- User
- Group
- external
- uri
type: string
example: Group
ErrorResponse2:
title: ErrorResponse
description: The error response.
type: object
required:
- status
- detail
properties:
schemas:
type: array
items:
type: string
example: urn:ietf:params:scim:api:messages:2.0:Error
description: The collection of error schemas.
status:
type: integer
example: 400
description: Status code for error.
detail:
type: string
example: Request is unparsable, syntactically incorrect, or violates schema.
description: Details of the error.
scimType:
$ref: '#/components/schemas/ErrorScimType'
Name:
title: Name
description: The name of the user.
type: object
required:
- givenName
- familyName
properties:
givenName:
type: string
description: The given/first name of the user.
example: Mike
minLength: 1
maxLength: 30
familyName:
type: string
description: The family/last name of the user.
example: Stuart
minLength: 1
maxLength: 50
middleName:
type: string
description: The middle name of the user.
example: A
maxLength: 30
honorificPrefix:
type: string
description: The prefix of the user.
example: Mr.
maxLength: 30
Mutability:
title: Mutability
description: This is used to denote the mutability of the attribute.
enum:
- readOnly
- readWrite
- immutable
- writeOnly
type: string
example: writeOnly
AttributeDataType:
title: AttributeDataType
description: This is used to denote the type of the attribute.
enum:
- st
# --- truncated at 32 KB (88 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-user-scim-api-openapi.yml