Cvent Event Cloud Venue Meeting Rooms API

Manage meeting rooms for a venue, including creating and updating room details, configuring capacities and amenities, and associating images.

Operations 5

POST /venues/{venueId}/meeting-rooms Create Meeting Room #
GET /venues/{venueId}/meeting-rooms/overviews List Meeting Rooms Overviews #
PUT /venues/{venueId}/meeting-rooms/{meetingRoomId} Update Meeting Room #
PATCH /venues/{venueId}/meeting-rooms/{meetingRoomId} Patch Meeting Room #
GET /venues/{venueId}/meeting-rooms/{meetingRoomId}/overview Get Meeting Room Overview #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/cvent-event-cloud-venue-meeting-rooms-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

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 Specification

cvent-event-cloud-venue-meeting-rooms-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cvent REST Venue Meeting Rooms 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 Meeting Rooms
  description: Manage meeting rooms for a venue, including creating and updating room details, configuring capacities and amenities, and associating images.
paths:
  /venues/{venueId}/meeting-rooms:
    post:
      operationId: createMeetingRoom
      summary: Create Meeting Room
      description: Create a new meeting room for the specified venue.
      security:
      - OAuth2.authorizationCode:
        - venue/meeting-rooms:write
      - OAuth2.clientCredentials:
        - venue/meeting-rooms:write
      parameters:
      - $ref: '#/components/parameters/venueId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/meetingRoom'
      tags:
      - Venue Meeting Rooms
      responses:
        '201':
          description: Meeting room created successfully.
          headers:
            Location:
              description: URL of the newly created meeting room.
              schema:
                type: string
                format: uri
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/existingMeetingRoom'
        '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}/meeting-rooms/overviews:
    get:
      operationId: listMeetingRoomsOverviews
      summary: List Meeting Rooms Overviews
      description: Retrieve a paginated list of meeting room overviews for the specified venue.
      security:
      - OAuth2.authorizationCode:
        - venue/meeting-room-overviews:read
      - OAuth2.clientCredentials:
        - venue/meeting-room-overviews:read
      parameters:
      - $ref: '#/components/parameters/venueId'
      - name: limit
        in: query
        required: false
        description: The maximum number of records to return per page.
        schema:
          type: integer
          minimum: 1
          maximum: 200
          default: 100
        example: 100
      - name: token
        in: query
        required: false
        description: The continuation token returned from a previous request. This must be a valid UUID v4 if provided. This will override any other pageable parameters provided.
        schema:
          type: string
          format: uuid
        example: 0e28af57-511f-47ab-ae46-46cd1ca51a1a
      - 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:


          * `hiddenOnProfile` (`eq`)

          '
        schema:
          type: string
        example: hiddenOnProfile eq 'false'
      tags:
      - Venue Meeting Rooms
      responses:
        '200':
          description: Successfully retrieved overview of meeting rooms.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/meetingRoomsOverviewResponse'
        '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}/meeting-rooms/{meetingRoomId}:
    put:
      operationId: updateMeetingRoom
      summary: Update Meeting Room
      description: Update a meeting room for the specified venue, replacing the existing meeting room data.
      security:
      - OAuth2.authorizationCode:
        - venue/meeting-rooms:write
      - OAuth2.clientCredentials:
        - venue/meeting-rooms:write
      parameters:
      - $ref: '#/components/parameters/venueId'
      - $ref: '#/components/parameters/meetingRoomId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/existingMeetingRoom'
      tags:
      - Venue Meeting Rooms
      responses:
        '200':
          description: Successfully updated the meeting room.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/existingMeetingRoom'
        '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: patchMeetingRoom
      summary: Patch Meeting Room
      description: 'Partially update a meeting room for the specified venue.


        - Only fields present in the request body are updated; omitted fields remain unchanged.

        - Set a field to `null` to unset it.

        - **Arrays (`capacities`, `amenities`) are treated as full replacements** — the entire array is replaced, not merged.

        - All changes are applied atomically.

        '
      security:
      - OAuth2.authorizationCode:
        - venue/meeting-rooms:write
      - OAuth2.clientCredentials:
        - venue/meeting-rooms:write
      parameters:
      - $ref: '#/components/parameters/venueId'
      - $ref: '#/components/parameters/meetingRoomId'
      requestBody:
        required: true
        content:
          application/merge-patch+json:
            schema:
              $ref: '#/components/schemas/patchMeetingRoom'
      tags:
      - Venue Meeting Rooms
      responses:
        '200':
          description: Successfully updated the meeting room.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/patchMeetingRoom'
        '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}/meeting-rooms/{meetingRoomId}/overview:
    get:
      operationId: getMeetingRoomOverview
      summary: Get Meeting Room Overview
      description: Retrieve an overview of a specific meeting room for the specified venue.
      security:
      - OAuth2.authorizationCode:
        - venue/meeting-room-overviews:read
      - OAuth2.clientCredentials:
        - venue/meeting-room-overviews:read
      parameters:
      - $ref: '#/components/parameters/venueId'
      - $ref: '#/components/parameters/meetingRoomId'
      tags:
      - Venue Meeting Rooms
      responses:
        '200':
          description: Successfully retrieved the meeting room overview.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/meetingRoomOverview'
        '401':
          $ref: '#/components/responses/Unauthorized1'
        '403':
          $ref: '#/components/responses/Forbidden1'
        '404':
          $ref: '#/components/responses/NotFound1'
        '429':
          $ref: '#/components/responses/TooManyRequests1'
components:
  schemas:
    MeetingRoomRate:
      title: Meeting Room Rate
      description: Meeting room rate with a value and application type.
      type: object
      properties:
        value:
          type: number
          description: The monetary value of the rate.
          minimum: 0
          maximum: 999999
          multipleOf: 0.01
          example: 500
        applicationType:
          $ref: '#/components/schemas/RateApplicationType'
      required:
      - value
      - applicationType
    MeetingRoomSeatingCapacity:
      title: Meeting Room Seating Capacity
      description: Maximum number of attendees for a specific seating style in a meeting room.
      type: object
      properties:
        layoutType:
          $ref: '#/components/schemas/SeatingLayoutType'
        maxAttendees:
          type: integer
          description: Maximum number of attendees for this seating style.
          minimum: 0
          maximum: 9999999
          example: 250
      required:
      - layoutType
      - maxAttendees
    meetingRoomOverview:
      title: Meeting Room Overview
      description: An overview of a venue meeting room containing key identifiers and display properties.
      type: object
      required:
      - id
      - name
      properties:
        id:
          type: string
          format: uuid
          description: The ID of the meeting room.
          readOnly: true
          example: b2c3d4e5-f6a7-8901-bcde-f12345678901
        name:
          type: string
          description: The display name of the meeting room.
          example: Grand Ballroom
        hiddenOnProfile:
          type: boolean
          description: True indicates the meeting room is hidden on the venue profile.
          example: false
        displayOrder:
          type: integer
          description: Position of this meeting room in the venue's room listing, with 1 being the first position.
          minimum: 1
          example: 1
    SeatingLayoutType:
      title: Seating Layout Type
      description: The seating arrangement style for a meeting room. Values represent standard event industry seating configurations.
      type: string
      enum:
      - BANQUET
      - CLASSROOM
      - COCKTAIL_ROUNDS
      - CONFERENCE
      - CRESCENT_ROUNDS
      - E_SHAPE
      - HOLLOW_SQUARE
      - MAXIMUM_CAPACITY
      - PERIMETER_SEATING
      - ROYAL_CONFERENCE
      - TALK_SHOW
      - THEATER
      - T_SHAPE
      - U_SHAPE
      example: THEATER
    AreaMeasurement:
      title: Area Measurement
      description: Measurement of area in square feet or square meters.
      type: object
      properties:
        value:
          type: number
          description: The numeric value of the area measurement.
          minimum: 1
          maximum: 9999999
          example: 1500
        unit:
          type: string
          description: The unit of measurement for the area.
          enum:
          - SQUARE_FEET
          - SQUARE_METERS
          example: SQUARE_FEET
      required:
      - value
      - unit
    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.
    VenueID:
      title: Venue ID
      description: A unique identifier for a venue
      type: string
      format: uuid
      example: 6bb0e2db-861f-46e3-a923-eb4d959ffa00
    ExhibitLayoutType:
      title: Exhibit Layout Type
      description: The exhibit setup type for a meeting room. Values represent standard exhibit booth and display configurations.
      type: string
      enum:
      - BOOTH_10x10
      - BOOTH_8x10
      - ISLAND_EXHIBIT
      - PENINSULA_EXHIBIT
      - PERIMETER_EXHIBIT
      - TABLETOP_EXHIBIT
      example: BOOTH_10x10
    meetingRoomsOverviewResponse:
      title: Meeting Rooms Overview Response
      description: Paginated overview of meeting rooms for a venue.
      type: object
      required:
      - data
      properties:
        paging:
          $ref: '#/components/schemas/Paging'
        data:
          type: array
          description: Overview of meeting rooms.
          minItems: 0
          maxItems: 200
          items:
            $ref: '#/components/schemas/meetingRoomOverview'
    MeetingRoomCapacities:
      title: Meeting Room Capacities
      description: Capacity information for a meeting room, grouped by category.
      type: object
      properties:
        exhibits:
          type: array
          description: Maximum number of exhibits per room setup.
          maxItems: 6
          items:
            $ref: '#/components/schemas/MeetingRoomExhibitCapacity'
        seating:
          type: array
          description: Maximum number of attendees per seating style.
          maxItems: 14
          items:
            $ref: '#/components/schemas/MeetingRoomSeatingCapacity'
    patchMeetingRoom:
      title: MeetingRoomPatch
      description: Partial update payload for a venue meeting room.
      type: object
      properties:
        name:
          type: string
          description: The name of the meeting room.
          example: Grand Ballroom
          minLength: 1
          maxLength: 100
        description:
          type:
          - string
          - 'null'
          description: The detailed description of the meeting room.
          example: Large conference space with natural lighting
          maxLength: 2500
        dimensions:
          type: object
          description: Physical dimensions for the meeting room.
          properties:
            totalSpace:
              $ref: '#/components/schemas/AreaMeasurement'
            ceilingHeight:
              $ref: '#/components/schemas/Dimension'
            length:
              $ref: '#/components/schemas/Dimension'
            width:
              $ref: '#/components/schemas/Dimension'
        displayOrder:
          type: integer
          description: The position of this meeting room in the venue's room listing.
          example: 1
          minimum: 1
        externalSourceId:
          type:
          - string
          - 'null'
          description: The provider's own identifier for this meeting room.
          example: EXT-RM-12345
          maxLength: 100
        rates:
          type:
          - object
          - 'null'
          description: Rate information for move in/out and events.
          properties:
            moveIn:
              $ref: '#/components/schemas/MeetingRoomRate'
            moveOut:
              $ref: '#/components/schemas/MeetingRoomRate'
            event:
              $ref: '#/components/schemas/MeetingRoomRate'
        capacities:
          type:
          - object
          - 'null'
          description: Capacity information for the meeting room, grouped by category.
          properties:
            exhibits:
              type:
              - array
              - 'null'
              description: Maximum number of exhibits per room setup.
              maxItems: 6
              items:
                $ref: '#/components/schemas/MeetingRoomExhibitCapacity'
            seating:
              type:
              - array
              - 'null'
              description: Maximum number of attendees per seating style.
              maxItems: 14
              items:
                $ref: '#/components/schemas/MeetingRoomSeatingCapacity'
        amenities:
          type:
          - array
          - 'null'
          description: List of amenities available in the meeting room.
          maxItems: 50
          items:
            $ref: '#/components/schemas/MeetingRoomAmenity'
        hiddenOnProfile:
          type: boolean
          description: True indicates the meeting room is hidden on the venue profile.
          example: false
    RateApplicationType:
      title: Rate Application Type
      description: 'How the rate is applied to the meeting room booking.


        Values:

        - `COMPLIMENTARY` — Complimentary

        - `INCLUDED` — Included

        - `ONETIME_FEE` — One-Time Fee

        - `PER_DAY` — Per Day

        - `PER_HOUR` — Per Hour

        - `PER_SQ_FT` — Per Square Foot

        - `PER_SQ_MTR` — Per Square Meter

        - `TOTAL` — Total'
      type: string
      enum:
      - COMPLIMENTARY
      - INCLUDED
      - ONETIME_FEE
      - PER_DAY
      - PER_HOUR
      - PER_SQ_FT
      - PER_SQ_MTR
      - TOTAL
      example: PER_DAY
    Paging:
      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/PaginationLinks'
    Link:
      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
    Audit:
      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
    existingMeetingRoom:
      title: Existing Meeting Room
      description: An existing venue meeting room with read-only generated properties.
      required:
      - id
      type: object
      allOf:
      - $ref: '#/components/schemas/meetingRoom'
      properties:
        id:
          type: string
          format: uuid
          description: The unique identifier for the meeting room.
          readOnly: true
          example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
    meetingRoom:
      title: Meeting Room
      description: A venue meeting room.
      allOf:
      - $ref: '#/components/schemas/Audit'
      type: object
      required:
      - name
      - dimensions
      properties:
        name:
          type: string
          description: The name of the meeting room.
          minLength: 1
          maxLength: 100
          example: Grand Ballroom
        description:
          type: string
          description: The detailed description of the meeting room.
          maxLength: 2500
          example: Large conference space with natural lighting
        dimensions:
          type: object
          description: Physical dimensions for the meeting room.
          required:
          - totalSpace
          properties:
            totalSpace:
              $ref: '#/components/schemas/AreaMeasurement'
            ceilingHeight:
              $ref: '#/components/schemas/Dimension'
            length:
              $ref: '#/components/schemas/Dimension'
            width:
              $ref: '#/components/schemas/Dimension'
        displayOrder:
          type: integer
          description: The position of this meeting room in the venue's room listing.
          minimum: 1
          example: 1
        externalSourceId:
          type: string
          description: The provider's own identifier for this meeting room.
          maxLength: 100
          example: EXT-123
        rates:
          type: object
          description: Rate information for move in/out and events.
          properties:
            moveIn:
              $ref: '#/components/schemas/MeetingRoomRate'
            moveOut:
              $ref: '#/components/schemas/MeetingRoomRate'
            event:
              $ref: '#/components/schemas/MeetingRoomRate'
        capacities:
          $ref: '#/components/schemas/MeetingRoomCapacities'
        amenities:
          type: array
          description: List of amenities available in the meeting room.
          maxItems: 50
          items:
            $ref: '#/components/schemas/MeetingRoomAmenity'
        hiddenOnProfile:
          type: boolean
          description: True indicates the meeting room is hidden on the venue profile.
          default: false
          example: false
    MeetingRoomExhibitCapacity:
      title: Meeting Room Exhibit Capacity
      description: Maximum number of exhibits for a specific exhibit layout type in a meeting room.
      type: object
      properties:
        layoutType:
          $ref: '#/components/schemas/ExhibitLayoutType'
        maxExhibits:
          type: integer
          description: Maximum number of exhibits for this layout type.
          minimum: 0
          maximum: 9999999
          example: 50
      required:
      - layoutType
      - maxExhibits
    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
    Pagin

# --- truncated at 32 KB (72 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cvent-event-cloud/refs/heads/main/openapi/cvent-event-cloud-venue-meeting-rooms-api-openapi.yml