Cvent Event Cloud Venue Profiles API
Manage venue profile details including type, contact information, address, and other venue properties.
Manage venue profile details including type, contact information, address, and other venue properties.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/cvent-event-cloud-venue-profiles-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Cvent REST Venue Profiles API
description: "# 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: Venue Profiles
description: Manage venue profile details including type, contact information, address, and other venue properties.
paths:
/venues/{venueId}/details:
put:
operationId: updateVenueDetails
summary: Update Venue Details
description: Update venue details for the specified venue, replacing the existing venue details data.
security:
- OAuth2.authorizationCode:
- venue/venue-details:write
- OAuth2.clientCredentials:
- venue/venue-details:write
parameters:
- $ref: '#/components/parameters/venueId'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/existingVenueDetails'
tags:
- Venue Profiles
responses:
'200':
description: Successfully updated the venue details.
content:
application/json:
schema:
$ref: '#/components/schemas/existingVenueDetails'
'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'
patch:
operationId: patchVenueDetails
summary: Patch Venue Details
description: 'Partially updates the specified venue''s details using JSON Merge Patch, as defined in [RFC 7396](https://www.rfc-editor.org/rfc/rfc7396.html).
- Only fields present in the request body are updated; omitted fields remain unchanged.
- Set a field to `null` to unset it.
- If any part of the patch fails, the entire request will fail.
**Array Handling:**
- Arrays (`locationTypes`) are treated as **full replacements**, not partial updates.
- If an array property is not included in the payload, no updates are made to that field.
- If an empty array is sent, it replaces the existing array with an empty array.
'
security:
- OAuth2.authorizationCode:
- venue/venue-details:write
- OAuth2.clientCredentials:
- venue/venue-details:write
parameters:
- $ref: '#/components/parameters/venueId'
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/venueDetailsPatch'
tags:
- Venue Profiles
responses:
'200':
description: Successfully updated the venue details. The response contains only the fields that were provided in the request payload.
content:
application/json:
schema:
$ref: '#/components/schemas/venueDetailsPatch'
'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'
/venues/{venueId}/details/overview:
get:
operationId: getVenueDetailsOverview
summary: Get Venue Details Overview
description: Retrieve an overview of venue details for the specified venue.
security:
- OAuth2.authorizationCode:
- venue/venue-details-overview:read
- OAuth2.clientCredentials:
- venue/venue-details-overview:read
parameters:
- $ref: '#/components/parameters/venueId'
tags:
- Venue Profiles
responses:
'200':
description: Successfully retrieved the venue details overview.
content:
application/json:
schema:
$ref: '#/components/schemas/venueDetailsOverview'
'401':
$ref: '#/components/responses/Unauthorized1'
'403':
$ref: '#/components/responses/Forbidden1'
'404':
$ref: '#/components/responses/NotFound1'
'429':
$ref: '#/components/responses/TooManyRequests1'
/venues/{venueId}/facility:
put:
operationId: updateVenueFacility
summary: Update Venue Facility
description: 'Update the facility information for the specified venue, replacing all existing values with those provided in the request body.
Field applicability varies by venue type:
- Most facility information fields do not apply to CVB/DMC or Restaurant venues.
'
security:
- OAuth2.authorizationCode:
- venue/venue-facility:write
- OAuth2.clientCredentials:
- venue/venue-facility:write
parameters:
- $ref: '#/components/parameters/venueId'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/existingVenueFacility'
tags:
- Venue Profiles
responses:
'200':
description: Successfully updated the venue facility information.
content:
application/json:
schema:
$ref: '#/components/schemas/existingVenueFacility'
'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'
patch:
operationId: patchVenueFacility
summary: Patch Venue Facility
description: 'Partially update the facility information for the specified venue using JSON Merge Patch, as defined in [RFC 7396](https://www.rfc-editor.org/rfc/rfc7396.html).
- Only fields present in the request body are updated; omitted fields remain unchanged.
- Set a field to `null` to unset it.
- If any part of the patch fails, the entire request will fail.
- `proximityFromAirport.unit` is required when `proximityFromAirport.distance` is provided.
Field applicability varies by venue type:
- Most facility information fields do not apply to CVB/DMC or Restaurant venues.
'
security:
- OAuth2.authorizationCode:
- venue/venue-facility:write
- OAuth2.clientCredentials:
- venue/venue-facility:write
parameters:
- $ref: '#/components/parameters/venueId'
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/venueFacilityPatch'
tags:
- Venue Profiles
responses:
'200':
description: Successfully updated the venue facility information. The response contains only the fields that were provided in the request payload.
content:
application/json:
schema:
$ref: '#/components/schemas/venueFacilityPatch'
'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:
schemas:
venueDetailsOverview:
title: Venue Details Overview
description: An overview of venue details containing key identifiers and display properties.
type: object
required:
- id
- name
properties:
id:
type: string
format: uuid
description: Venue ID.
readOnly: true
example: b2c3d4e5-f6a7-8901-bcde-f12345678901
name:
type: string
description: Venue name.
maxLength: 100
example: Vienna Wolf Trap Hotel
venueDetailsPatch:
title: VenueDetailsPatch
description: Partial update payload for venue details.
type: object
properties:
type:
$ref: '#/components/schemas/VenueType'
timeZone:
type:
- string
- 'null'
description: Time zone identifier for the venue. See the supported timezones reference for valid values.
example: America/New_York
externalDocs:
description: Supported Timezones
url: https://developers.cvent.com/docs/rest-api/reference/api-standards#supported-timezones
brand:
type:
- string
- 'null'
description: Venue brand. Brands vary by venue type.
example: Quality Hotels
maxLength: 100
chainScale:
type:
- string
- 'null'
allOf:
- $ref: '#/components/schemas/ChainScale'
mainPhoneNumber:
type: string
description: Primary phone number for the venue.
example: +1-703-555-0100
minLength: 1
maxLength: 30
mainFaxNumber:
type: string
description: Primary fax number for the venue.
example: +1-703-555-0101
minLength: 1
maxLength: 30
salesPhoneNumber:
type:
- string
- 'null'
description: Sales phone number of the venue.
example: +1-703-555-0102
maxLength: 30
salesFaxNumber:
type:
- string
- 'null'
description: Sales fax number of the venue.
example: +1-703-555-0103
maxLength: 30
tollFreeNumber:
type:
- string
- 'null'
description: Toll-free number of the venue.
example: 1-800-555-0100
maxLength: 30
websiteAddress:
type:
- string
- 'null'
format: uri
description: Website address.
maxLength: 300
example: https://www.example-hotel.com
currency:
type:
- string
- 'null'
allOf:
- $ref: '#/components/schemas/Currency'
openingDate:
type:
- string
- 'null'
description: Venue opening date as free-form text.
example: Spring 2025
maxLength: 30
description:
type:
- string
- 'null'
description: Venue description.
example: A premier conference and event venue in the heart of Northern Virginia.
maxLength: 4000
additionalInformation:
type:
- string
- 'null'
description: Additional information about the venue.
example: Complimentary parking available for all event attendees.
maxLength: 2500
cancellationPolicy:
type:
- string
- 'null'
description: Cancellation policy for bookings at the venue.
example: 48-hour cancellation policy applies for all event bookings.
maxLength: 2500
locationTypes:
type:
- array
- 'null'
description: Location classifications.
maxItems: 6
items:
$ref: '#/components/schemas/LocationType'
address:
type:
- object
- 'null'
description: Venue address information.
properties:
streetAddress1:
type:
- string
- 'null'
description: Street address line 1.
example: 1234 Trap Road
maxLength: 40
streetAddress2:
type:
- string
- 'null'
description: Street address line 2.
example: Suite 100
maxLength: 40
city:
type: string
description: City.
minLength: 1
maxLength: 40
example: Vienna
stateProvince:
$ref: '#/components/schemas/StateProvince1'
zipPostalCode:
type:
- string
- 'null'
description: ZIP or postal code.
example: '22182'
maxLength: 25
country:
$ref: '#/components/schemas/Country'
directions:
type:
- string
- 'null'
description: Directions or instructions for getting to the venue.
example: Take I-66 West to Exit 67, then follow signs to Trap Road.
maxLength: 2500
Country:
title: Country
description: ISO 3166 two-letter (alpha-2) country codes with some additional non-standard cvent specific codes.
type: string
enum:
- BLANK
- AD
- AE
- AF
- AG
- AI
- AL
- AM
- AN
- AO
- AQ
- AR
- AS
- AT
- AU
- AW
- AX
- AZ
- BA
- BB
- BD
- BE
- BF
- BG
- BH
- BI
- BJ
- BL
- BM
- BN
- BO
- BQ
- BR
- BS
- BT
- BV
- BW
- BY
- BZ
- CA
- CC
- CD
- CF
- CG
- CH
- CI
- CK
- CL
- CM
- CN
- CO
- CR
- CU
- CV
- CW
- CX
- CY
- CZ
- DE
- DJ
- DK
- DM
- DO
- DZ
- EC
- EE
- EG
- EH
- ER
- ES
- ET
- FI
- FJ
- FK
- FM
- FO
- FR
- GA
- GB
- GB_1
- GB_2
- GB_3
- GB_4
- GD
- GE
- GF
- GG
- GH
- GI
- GL
- GM
- GN
- GP
- GQ
- GR
- GS
- GT
- GU
- GW
- GY
- HK
- HM
- HN
- HR
- HT
- HU
- ID
- IE
- IL
- IM
- IN
- IO
- IQ
- IR
- IS
- IT
- JE
- JM
- JO
- JP
- KE
- KG
- KH
- KI
- KM
- KN
- KO
- KP
- KR
- KW
- KY
- KZ
- LA
- LB
- LC
- LI
- LK
- LR
- LS
- LT
- LU
- LV
- LY
- MA
- MC
- MD
- ME
- MF
- MG
- MH
- MK
- ML
- MM
- MN
- MO
- MP
- MQ
- MR
- MS
- MT
- MU
- MV
- MW
- MX
- MY
- MZ
- NA
- NC
- NE
- NF
- NG
- NI
- NL
- 'NO'
- NP
- NR
- NU
- NZ
- OM
- PA
- PE
- PF
- PG
- PH
- PK
- PL
- PM
- PN
- PR
- PS
- PT
- PW
- PY
- QA
- RE
- RO
- RS
- RU
- RW
- SA
- SB
- SC
- SD
- SE
- SG
- SH
- SI
- SJ
- SK
- SL
- SM
- SN
- SO
- SR
- SS
- ST
- SV
- SX
- SY
- SZ
- TC
- TD
- TF
- TG
- TH
- TJ
- TK
- TL
- TM
- TN
- TO
- TP
- TR
- TT
- TV
- TW
- TZ
- UA
- UG
- UM
- US
- UY
- UZ
- VA
- VC
- VE
- VG
- VI
- VN
- VU
- WF
- WS
- YE
- YT
- ZA
- ZM
- ZW
venueFacilityPatch:
title: VenueFacilityPatch
description: Partial update payload for venue facility information. Only fields present in the request body are updated; omitted fields remain unchanged. Set leaf fields to `null` to unset them. For grouped objects, update or clear each child field explicitly instead of setting the entire group to `null`. Field applicability varies by venue type; values supplied for fields that do not apply to the venue's type will be rejected.
type: object
properties:
numberOfMeetingRooms:
type:
- integer
- 'null'
description: Total number of meeting rooms at the venue.
minimum: 0
maximum: 10000
example: 25
space:
type: object
description: Facility space measurements at the venue.
properties:
unitOfMeasurement:
type:
- string
- 'null'
allOf:
- $ref: '#/components/schemas/MeasurementUnit'
totalMeetingRoomSpace:
type:
- integer
- 'null'
description: Total meeting room space at the venue.
minimum: 0
maximum: 99999999
example: 50000
totalExhibitSpace:
type:
- integer
- 'null'
description: Total exhibit space at the venue.
minimum: 0
maximum: 99999999
example: 75000
sleeping:
type: object
description: Sleeping room inventory at the venue.
properties:
totalRooms:
type:
- integer
- 'null'
description: Total number of sleeping rooms at the venue.
minimum: 0
maximum: 10000
example: 350
suites:
type:
- integer
- 'null'
description: Total number of suites at the venue.
minimum: 0
maximum: 10000
example: 20
singleRooms:
type:
- integer
- 'null'
description: Total number of single-occupancy rooms at the venue.
minimum: 0
maximum: 10000
example: 200
doubleRooms:
type:
- integer
- 'null'
description: Total number of double-occupancy rooms at the venue.
minimum: 0
maximum: 10000
example: 130
singleRate:
type: object
description: Published rate range for single-occupancy rooms, expressed in the venue's configured currency.
properties:
low:
type:
- number
- 'null'
description: Lowest published rate for a single-occupancy room.
minimum: 0
maximum: 999999999
example: 129.99
high:
type:
- number
- 'null'
description: Highest published rate for a single-occupancy room.
minimum: 0
maximum: 999999999
example: 249.99
doubleRate:
type: object
description: Published rate range for double-occupancy rooms, expressed in the venue's configured currency.
properties:
low:
type:
- number
- 'null'
description: Lowest published rate for a double-occupancy room.
minimum: 0
maximum: 999999999
example: 149.99
high:
type:
- number
- 'null'
description: Highest published rate for a double-occupancy room.
minimum: 0
maximum: 999999999
example: 299.99
taxRate:
type:
- number
- 'null'
description: Tax rate applied at the venue, expressed as a percentage.
minimum: 0
maximum: 999999999
example: 8.5
occupancyRate:
type:
- number
- 'null'
description: Occupancy rate at the venue, expressed as a percentage.
minimum: 0
maximum: 999999999
example: 75.5
yearBuilt:
type:
- integer
- 'null'
description: Four-digit year the venue was built.
minimum: 0
maximum: 9999
example: 1998
yearRenovated:
type:
- integer
- 'null'
description: Four-digit year the venue was last renovated.
minimum: 0
maximum: 9999
example: 2021
proximityFromAirport:
type: object
description: Distance from the nearest airport. `unit` is required when `distance` is provided.
properties:
distance:
type:
- number
- 'null'
description: Distance from the nearest airport, expressed in `unit`. Up to four digits.
minimum: 0
maximum: 9999
example: 12.5
unit:
type:
- string
- 'null'
allOf:
- $ref: '#/components/schemas/DistanceMeasurementUnit'
restrictions:
type:
- string
- 'null'
description: Free-form description of any facility restrictions at the venue.
maxLength: 2500
example: No outside food or beverage permitted. Music must end by 11 PM.
maximumCapacity:
type: object
description: 'Maximum attendee capacity at the venue. Applicable only to venue types: Aquarium/Zoo, Arena/Stadium, Banquet Facility, Bar/Club, Corporate Office Space, Educational Facility, Entertainment Venue, Gallery/Museum, Golf Course, Movie Theatre, and Special Event Venue.'
properties:
seated:
type:
- integer
- 'null'
description: Maximum seated capacity at the venue.
minimum: 0
maximum: 10000
example: 500
standing:
type:
- integer
- 'null'
description: Maximum standing capacity at the venue.
minimum: 0
maximum: 10000
example: 800
eventInsurance:
type:
- string
- 'null'
allOf:
- $ref: '#/components/schemas/EventInsurance'
venueDetails:
title: VenueDetails
description: Venue details model.
allOf:
- $ref: '#/components/schemas/Audit'
type: object
required:
- type
- mainPho
# --- truncated at 32 KB (100 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-venue-profiles-api-openapi.yml