Bright Pattern · OpenAPI Overlay 1.0.0

API Evangelist enhancements for BPCC Mobile/Web Messaging API v2

3 actions 3 updates update extends openapi/bright-pattern-mobile-web-messaging-v2-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Bright Pattern's API. It is a proposal applied on top of the contract, not a document Bright Pattern publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-artifactsx-operation-countx-multi-tenantx-tenant-notex-authorization-model

Targets 3

$.info
$.servers[0]
$.components.securitySchemes.bearerAuth

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements for BPCC Mobile/Web Messaging API v2
  version: 1.0.0
extends: openapi/bright-pattern-mobile-web-messaging-v2-openapi.yml
x-generated: '2026-08-08'
x-method: generated
x-note: Captures the API Evangelist enrichment layer over the derived specification. The specification
  itself is a mechanical conversion of the Postman collection Bright Pattern publishes; this overlay records
  what API Evangelist added on top and is never merged back into the source.
actions:
- target: $.info
  update:
    x-apievangelist-provider: bright-pattern
    x-apievangelist-artifacts:
      authentication: authentication/bright-pattern-authentication.yml
      conventions: conventions/bright-pattern-conventions.yml
      errors: errors/bright-pattern-problem-types.yml
      lifecycle: lifecycle/bright-pattern-lifecycle.yml
      conformance: conformance/bright-pattern-conformance.yml
      data_model: data-model/bright-pattern-data-model.yml
      postman_source: postman/bright-pattern-postman.yml
    x-operation-count: 16
- target: $.servers[0]
  update:
    x-multi-tenant: true
    x-tenant-note: The base host is the customer contact-center tenant domain; there is no shared production
      host.
- target: $.components.securitySchemes.bearerAuth
  update:
    x-authorization-model: privilege-based (contact-center user role privileges), not OAuth scopes