Omnisend · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Omnisend events-api

4 actions 4 updates documentation extends omnisend-events-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Omnisend's API. It is a proposal applied on top of the contract, not a document Omnisend publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

tagssecurityoperationId

Targets 2

$
$.paths['/events'].post

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements for Omnisend events-api
  version: 1.0.0
  x-generated: '2026-08-13'
  x-method: generated
  x-source: openapi/omnisend-events-api-openapi.yml
  x-note: 'Records API Evangelist enhancements over the contract Omnisend publishes. It is never applied to the harvested
    file — openapi/ stays verbatim. The gaps captured here are real and measured: 1 of 1 operations carry no operationId,
    0 carry no tag, and the document declares securitySchemes without ever applying them.'
extends: omnisend-events-api-openapi.yml
actions:
- target: $
  description: Apply the two declared security schemes at the document root. The published contract defines ApiKeyAuth and
    Bearer in components.securitySchemes but never applies them, so no operation states its auth requirement.
  update:
    security:
    - ApiKeyAuth: []
    - Bearer: []
- target: $
  description: Declare a document-level tag so every operation can be grouped. The published contract declares none.
  update:
    tags:
    - name: Events
      description: ''
- target: $.paths['/events'].post
  description: Tag POST /events as Events.
  update:
    tags:
    - Events
- target: $.paths['/events'].post
  description: Add a stable operationId for POST /events; the published contract omits it, which blocks code generation and
    tool binding.
  update:
    operationId: post_events