Bell Canada · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Bell Canada Trouble Ticket API

3 actions 3 updates update extends openapi/bell-canada-trouble-ticket-api-openapi.json

Generated by API Evangelist Written by API Evangelist tooling for Bell Canada's API. It is a proposal applied on top of the contract, not a document Bell Canada publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-human-urlx-apievangelist-standardx-apievangelist-vendor-versionx-apievangelist-releasedx-apievangelist-last-updatedx-apievangelist-accessx-apievangelist-artifacts

Targets 3

$.info

$.host

OpenAPI Overlay

overlay: 1.0.0
info:
  title: API Evangelist enhancements for Bell Canada Trouble Ticket API
  version: 1.0.0
extends: openapi/bell-canada-trouble-ticket-api-openapi.json
x-generated: '2026-07-25'
x-method: generated
x-source: >-
  https://developer.bell.ca + openapi/*.json. This overlay records API Evangelist enhancements only.
  The harvested Swagger 2.0 document is never mutated.
actions:
- target: $.info
  update:
    x-apievangelist-provider: bell-canada
    x-apievangelist-human-url: https://developer.bell.ca/troubleticket
    x-apievangelist-standard: TM Forum TMF621 v4.1.1
    x-apievangelist-vendor-version: 'v2.5'
    x-apievangelist-released: '2021-03-19'
    x-apievangelist-last-updated: '2023-07-22'
    x-apievangelist-access: partner-gated
    x-apievangelist-artifacts:
      authentication: authentication/bell-canada-authentication.yml
      conventions: conventions/bell-canada-conventions.yml
      errors: errors/bell-canada-problem-types.yml
      lifecycle: lifecycle/bell-canada-lifecycle.yml
      sandbox: sandbox/bell-canada-sandbox.yml
      webhooks: asyncapi/bell-canada-webhooks.yml
      data_model: data-model/bell-canada-data-model.yml
      conformance: conformance/bell-canada-conformance.yml
      examples: examples/bell-canada-examples.yml
      skills: skills/_index.yml
- target: $.host
  description: >-
    The published document declares host "serverRoot", a placeholder. Bell emails the real endpoint
    to a partner after the registration form is approved, so no production host can be substituted
    here without fabricating one. Recorded, not replaced.
  update: {}
- target: $
  update:
    x-apievangelist-base-path: '/tmf-api/troubleTicket/v4/'
    x-apievangelist-host-published: false
    x-apievangelist-security-note: >-
      No securityDefinitions block exists in the published document. The credential is an API key
      supplied in a header the docs redact as the literal placeholder SECURITY_CREDENTIALS, plus
      x-external-system in sandbox. See authentication/bell-canada-authentication.yml.
    x-apievangelist-idempotency: none
    x-apievangelist-rate-limits: not-published