Renaissance · OpenAPI Overlay 1.0.0

API Evangelist enhancements — Renaissance Student Pathway Event Proxy

4 actions 4 updates servers extends ../openapi/renaissance-student-pathway-event-proxy-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Renaissance's API. It is a proposal applied on top of the contract, not a document Renaissance publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

contactserversbearerFormatx-issuerx-idempotencyx-reversibilityx-api-evangelist-note

Targets 4

$.info
$
$.components.securitySchemes.HTTPBearer
$.paths['/freckle-events'].post

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements — Renaissance Student Pathway Event Proxy
  version: 1.0.0
extends: ../openapi/renaissance-student-pathway-event-proxy-openapi.yml
x-generated: '2026-09-13'
x-method: generated
x-source: Derived from a probe of https://events.proficiency.renaissance.com/openapi.json
actions:
  - target: $.info
    update:
      contact:
        name: Renaissance Learning, Inc.
        url: https://www.renaissance.com/about-us/contact-renaissance/
  - target: $
    update:
      servers:
        - url: https://events.proficiency.renaissance.com
          description: Production host the contract is served from; the original declares no servers[].
  - target: $.components.securitySchemes.HTTPBearer
    update:
      bearerFormat: JWT
      x-issuer: https://auth.renaissance.com
  - target: $.paths['/freckle-events'].post
    update:
      x-idempotency: none
      x-reversibility: none
      x-api-evangelist-note: >-
        The only genuine write in the Renaissance contract set. It answers 202 with no returned
        identifier, declares no Idempotency-Key header and publishes no retraction path, so a client
        retrying a timed-out post cannot tell whether the first event landed.