Cvent Event Cloud · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Cvent REST RFP Management API

4 actions 4 updates phrasing extends openapi/cvent-event-cloud-rfp-management-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Cvent Event Cloud's API. It is a proposal applied on top of the contract, not a document Cvent Event Cloud publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/rfps/lead-sources/{leadSourceId}'].get
$.paths['/rfps/lead-sources/{leadSourceId}/sections/{leadSourceSectionId}'].get
$.paths['/rfps/{rfpId}'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Cvent REST RFP Management API
  version: 1.0.0
extends: openapi/cvent-event-cloud-rfp-management-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/rfps/lead-sources/{leadSourceId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an RFP lead source
      effect: read
      questions:
      - Where did an RFP originate, such as which software or website?
      - Can I look up the details of an RFP lead source?
      instructions:
      - text: Get RFP lead source {leadSourceId}.
        slots:
          leadSourceId: path.leadSourceId
      - text: Show where lead source {leadSourceId} comes from.
        slots:
          leadSourceId: path.leadSourceId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/rfps/lead-sources/{leadSourceId}/sections/{leadSourceSectionId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an RFP lead source section
      effect: read
      questions:
      - Which specific form or domain within a lead source did an RFP come through?
      - Can I get the section details of an RFP lead source?
      instructions:
      - text: Get section {leadSourceSectionId} of lead source {leadSourceId}.
        slots:
          leadSourceSectionId: path.leadSourceSectionId
          leadSourceId: path.leadSourceId
      - text: Show the channel for lead source section {leadSourceSectionId} under {leadSourceId}.
        slots:
          leadSourceSectionId: path.leadSourceSectionId
          leadSourceId: path.leadSourceId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/rfps/{rfpId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an RFP
      effect: read
      questions:
      - Can I pull the basic details of a venue sourcing RFP?
      - Is it possible to expand related entities when reading an RFP?
      instructions:
      - text: Get RFP {rfpId}.
        slots:
          rfpId: path.rfpId
      - text: Get RFP {rfpId} expanded with {expand}.
        slots:
          rfpId: path.rfpId
          expand: query.expand
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/cvent-event-cloud-rfp-management-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.