Bell Canada notification listeners (client side) API

The notification listeners (client side) API from Bell Canada — 31 operation(s) for notification listeners (client side).

Operations 31

POST /listener/changeRequestCreateEvent Client listener for entity ChangeRequestCreateEvent #
POST /listener/changeRequestStatusChangeEvent Client listener for entity ChangeRequestStatusChangeEvent #
POST /listener/changeRequestDeleteEvent Client listener for entity ChangeRequestDeleteEvent #
POST /listener/changeRequestAttributeValueChangeEvent Client listener for entity ChangeRequestAttributeValueChangeEvent #
POST /listener/changeRequestApprovalRequiredEvent Client listener for entity ChangeRequestApprovalRequiredEvent #
POST /listener/changeRequestFailureEvent Client listener for entity ChangeRequestFailureEvent #
POST /listener/resourceCreateEvent Client listener for entity ResourceCreateEvent #
POST /listener/resourceAttributeValueChangeEvent Client listener for entity ResourceAttributeValueChangeEvent #
POST /listener/resourceStateChangeEvent Client listener for entity ResourceStateChangeEvent #
POST /listener/resourceDeleteEvent Client listener for entity ResourceDeleteEvent #
POST /listener/physicalResourceCreateEvent Client listener for entity PhysicalResourceCreateEvent #
POST /listener/physicalResourceAttributeValueChangeEvent Client listener for entity PhysicalResourceAttributeValueChangeEvent #
POST /listener/physicalResourceStateChangeEvent Client listener for entity PhysicalResourceStateChangeEvent #
POST /listener/physicalResourceDeleteEvent Client listener for entity PhysicalResourceDeleteEvent #
POST /listener/serviceOrderCreateEvent Client listener for entity ServiceOrderCreateEvent #
POST /listener/serviceOrderAttributeValueChangeEvent Client listener for entity ServiceOrderAttributeValueChangeEvent #
POST /listener/serviceOrderStateChangeEvent Client listener for entity ServiceOrderStateChangeEvent #
POST /listener/serviceOrderDeleteEvent Client listener for entity ServiceOrderDeleteEvent #
POST /listener/serviceOrderInformationRequiredEvent Client listener for entity ServiceOrderInformationRequiredEvent #
POST /listener/serviceOrderMilestoneEvent Client listener for entity ServiceOrderMilestoneEvent #
POST /listener/serviceOrderJeopardyEvent Client listener for entity ServiceOrderJeopardyEvent #
POST /listener/cancelServiceOrderCreateEvent Client listener for entity CancelServiceOrderCreateEvent #
POST /listener/cancelServiceOrderStateChangeEvent Client listener for entity CancelServiceOrderStateChangeEvent #
POST /listener/cancelServiceOrderInformationRequiredEvent Client listener for entity CancelServiceOrderInformationRequiredEvent #
POST /listener/serviceOrderFailureEvent Client listener for entity ServiceOrderFailureEvent #
POST /listener/troubleTicketCreateEvent Client listener for entity TroubleTicketCreateEvent #
POST /listener/troubleTicketAttributeValueChangeEvent Client listener for entity TroubleTicketAttributeValueChangeEvent #
POST /listener/troubleTicketStatusChangeEvent Client listener for entity TroubleTicketStatusChangeEvent #
POST /listener/troubleTicketDeleteEvent Client listener for entity TroubleTicketDeleteEvent #
POST /listener/troubleTicketResolvedEvent Client listener for entity TroubleTicketResolvedEvent #
POST /listener/troubleTicketInformationRequiredEvent Client listener for entity TroubleTicketInformationRequiredEvent #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/bell-canada-notification-listeners-client-side-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

bell-canada-notification-listeners-client-side-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Bell Canada notification listeners (client side) API
  version: '1.0'
  description: 'Operations tagged notification listeners (client side) across 4 of this provider''s published API definitions: bell-canada-change-management-api-openapi.json, bell-canada-resource-inventory-api-openapi.json, bell-canada-service-order-api-openapi.json, bell-canada-trouble-ticket-api-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://serverRoot/tmf-api/ChangeManagement/v4/
- url: https://serverRoot/resourceInventoryManagement/v4/
- url: https://serverRoot/tmf-api/serviceOrdering/v4
- url: https://serverRoot/tmf-api/troubleTicket/v4/
tags:


# --- truncated at 32 KB (165 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/openapi/bell-canada-notification-listeners-client-side-api-openapi.yml