Cvent Social Tables · OpenAPI Overlay 1.0.0

API Evangelist enhancements — Social Tables API Gateway Authentication Events API

8 actions 8 updates documentation extends openapi/cvent-social-tables-events-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Cvent Social Tables's API. It is a proposal applied on top of the contract, not a document Cvent Social Tables publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

operationIdcontactx-support-channelexternalDocs

Targets 8

$.info
$
$.paths['/4.0/events'].get
$.paths['/4.0/events'].post
$.paths['/4.0/events/{event}'].delete
$.paths['/4.0/events/{event}'].get
$.paths['/4.0/events/{event}'].put
$.paths['/4.0/events/page'].get

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements — Social Tables API Gateway Authentication Events API
  version: 1.0.0
x-provenance:
  generated: '2026-09-07'
  method: generated
  source: openapi/cvent-social-tables-events-api-openapi.yml
  note: Overlay of API Evangelist enhancements over the provider contract. It never mutates the original.
    operationId values are GENERATED from method+path — they are not names Social Tables publishes; the
    provider declares no operationId on any of its 87 operations. contact and externalDocs are the provider's
    own real URLs.
extends: openapi/cvent-social-tables-events-api-openapi.yml
actions:
- target: $.info
  description: Point the contract at the developer portal that publishes it.
  update:
    contact:
      name: Social Tables Developer Portal
      url: https://developer.socialtables.com
    x-support-channel: Stack Overflow tag social-tables (https://developer.socialtables.com/docs/support/)
- target: $
  description: Attach the human documentation that explains auth, identifiers and permissions.
  update:
    externalDocs:
      description: Socialtables Developer Documentation
      url: https://developer.socialtables.com/docs/
- target: $.paths['/4.0/events'].get
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: get_events
- target: $.paths['/4.0/events'].post
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: create_events
- target: $.paths['/4.0/events/{event}'].delete
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: delete_events_By_Event
- target: $.paths['/4.0/events/{event}'].get
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: get_events_By_Event
- target: $.paths['/4.0/events/{event}'].put
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: replace_events_By_Event
- target: $.paths['/4.0/events/page'].get
  description: Add a stable operationId. The published Swagger 2.0 declares none, so generated clients
    produce machine-named methods.
  update:
    operationId: get_events_page