# Bell Canada

> Bell Canada is Canada's largest communications company and the principal operating subsidiary of BCE Inc. Its public API surface is a single suite of four TM Forum Open API aligned B2B service-management interfaces published at developer.bell.ca for enterprise and wholesale partners. Documentation and Swagger 2.0 definitions are public and downloadable without a login; access to any live endpoint is not — Bell issues credentials and the API endpoint by email after a manual review of a business registration.

Generated by API Evangelist from the Bell Canada developer portal and the four published Swagger documents. Provenance: generated 2026-07-25, method generated, source apis.yml + repo artifacts. Bell publishes no llms.txt of its own (developer.bell.ca returns its Next.js HTML shell with a 200 status for /llms.txt and for every /.well-known/ path).

## What you can and cannot do

- The four APIs below are REST over HTTPS, Swagger 2.0, TM Forum Open API v4.
- There is no public base URL. Every Swagger document declares `host: serverRoot`, a placeholder. api.bell.ca resolves to a live Bell API gateway but provisions no public route.
- Authentication is an API key supplied in a header that the docs redact as the literal placeholder `SECURITY_CREDENTIALS`. In sandbox, also send `x-external-system` with any unique value of 8+ characters.
- There is no OAuth 2.0, no OpenID Connect discovery, no scopes, no self-serve signup, no API console and no rate-limit policy.
- There is no idempotency key. Do not assume retries are safe.
- Bell publishes no CAMARA / GSMA Open Gateway API. Its network signals (Number Verification, SIM Swap) reach developers through EnStream LP and Aduna, not through Bell.

## APIs

- [Trouble Ticket (TMF621 v4.1.1, Bell v2.5)](https://developer.bell.ca/troubleticket): create, retrieve, list, patch and delete trouble tickets against Bell services from an ITSM or fault-management system; 6 notification events.
- [Service Order (TMF641 v4.6, Bell v1.4)](https://developer.bell.ca/serviceorder): place, amend, cancel and track service requests; serviceOrder and cancelServiceOrder resources; 11 notification events. Bell marks GetServiceOrder and GetServiceOrderList "Currently not available".
- [Resource Inventory Management (TMF639 v4.1, Bell v1.6)](https://developer.bell.ca/resourceinventory): query and maintain logical, physical and generic resource records; 8 notification events.
- [Change Management (TMF655 v4.2, Bell v1.1)](https://developer.bell.ca/changemanagement): raise, update, retrieve and list change requests with planned windows, risk and impact; 6 notification events.

## Specs

- [Trouble Ticket Swagger 2.0](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/openapi/bell-canada-trouble-ticket-api-openapi.json)
- [Service Order Swagger 2.0](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/openapi/bell-canada-service-order-api-openapi.json)
- [Resource Inventory Swagger 2.0](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/openapi/bell-canada-resource-inventory-api-openapi.json)
- [Change Management Swagger 2.0](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/openapi/bell-canada-change-management-api-openapi.json)
- [Trouble Ticket PDF specification](https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf)
- [Service Order PDF specification](https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf)
- [Resource Inventory PDF specification](https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf)
- [Change Management PDF specification](https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf)

## Docs

- [Developer portal](https://developer.bell.ca)
- [API overview](https://developer.bell.ca/overview)
- [Service Management suite](https://developer.bell.ca/servicemanagement)
- [API FAQ — access, keys, sandbox, standards, cost](https://developer.bell.ca/faq/apis)
- [Register for access](https://developer.bell.ca/register)
- [Contact](https://developer.bell.ca/contact)
- [Articles](https://developer.bell.ca/article)

## API Evangelist artifacts

- [Authentication profile](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/authentication/bell-canada-authentication.yml)
- [API conventions](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/conventions/bell-canada-conventions.yml)
- [Error catalogue](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/errors/bell-canada-problem-types.yml)
- [Lifecycle and versioning](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/lifecycle/bell-canada-lifecycle.yml)
- [Sandbox](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/sandbox/bell-canada-sandbox.yml)
- [Webhook / event catalogue](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/asyncapi/bell-canada-webhooks.yml)
- [Data model](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/data-model/bell-canada-data-model.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/conformance/bell-canada-conformance.yml)
- [Candidate MCP tool set](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/mcp/bell-canada-mcp.yml)
- [Agent skills](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/skills/_index.yml)
- [Agentic access contracts](https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/agentic-access/bell-canada-agentic-access.yml)

## Optional

- [BCE Inc. (parent)](https://www.bce.ca)
- [Bell Canada](https://www.bell.ca)
- [github.com/bellcanada](https://github.com/bellcanada) — verified organization, 0 public repositories
- [EnStream LP](https://enstream.com/) — the Bell / Rogers / TELUS identity and fraud-signal joint venture through which Bell network signals reach developers