How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bell Canada events subscription API

The events subscription API from Bell Canada — 2 operation(s) for events subscription.

Bell Canada events subscription API is one of 9 APIs that Bell Canada publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include events subscription. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://serverRoot/tmf-api/ChangeManagement/v4/, https://serverRoot/resourceInventoryManagement/v4/, https://serverRoot/tmf-api/serviceOrdering/v4, https://serverRoot/tmf-api/troubleTicket/v4/.

2 operations 2 paths 4 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Servers
https://serverRoot/tmf-api/ChangeManagement/v4/
https://serverRoot/resourceInventoryManagement/v4/
https://serverRoot/tmf-api/serviceOrdering/v4
https://serverRoot/tmf-api/troubleTicket/v4/
Resource Areas
1

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.

events subscription 2
POST
/hub
Register a listener
registerListener body → 201400401403404405409500
DELETE
/hub/{id}
Unregister a listener
unregisterListener 1 param → 204400401403404405500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Entity (3 properties), EventSubscription (3 properties), EventSubscriptionInput (2 properties). Each schema is shown below with its type and property counts.

EventSubscription
object
Sets the communication endpoint address the service instance must use to deliver notification information
3 properties 2 required
Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
EventSubscriptionInput
object
Sets the communication endpoint address the service instance must use to deliver notification information
2 properties 1 required
Entity
object
Base entity schema for use in TMForum Open-APIs
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bell-canada-events-subscription-api-openapi.yml Raw ↑

Other APIs Bell Canada publishes across the network.

Bell Canada Cancel Service Order API
Bell Canada Change Request API
Bell Canada Logical Resource API
Bell Canada notification listeners (client side) API
Bell Canada Physical Resource API
Bell Canada Resource API
Bell Canada Service Order API
Bell Canada Trouble Ticket API
Where this information came from

This is an independent, third-party profile of Bell Canada events subscription API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.