Bell Canada

Bell Canada is Canada's largest communications company and the principal operating subsidiary of BCE Inc., providing wireless, wireline, internet, television and enterprise network services across Canada, and operating Bell Media as the country's largest broadcaster. As a facilities-based mobile network operator and broadband carrier it sits at the connectivity layer of the telecom value chain, and its public API posture reflects that: Bell runs a real developer portal at developer.bell.ca whose only published API suite is a set of four TM Forum Open API aligned B2B service management interfaces — Trouble Ticket (TMF621), Service Order (TMF641), Resource Inventory (TMF639) and Change Management (TMF655) — for enterprise and wholesale partners integrating their ITSM systems with Bell. The Swagger 2.0 definitions and PDF specifications are downloadable without a login, but access to the sandbox and to any live endpoint requires a business registration form and manual approval; no base URL, no credential scheme and no self-serve key issuance is published, and the documented request examples redact the credential as a literal SECURITY_CREDENTIALS placeholder. Bell publishes no first-party CAMARA network APIs and runs no Open Gateway portal of its own. Its network APIs reach developers indirectly, through EnStream LP — the identity and fraud-signal joint venture Bell Mobility owns with Rogers and TELUS — which announced a partnership with Aduna, the Ericsson-and-carrier joint venture, on 27 February 2025 to distribute Canadian Number Verification and SIM Swap signals through Aduna's CAMARA-aligned global channel. Bell is therefore an aggregator-mediated carrier: partner-gated on its own surface, reachable by developers only through a third party.

Bell Canada publishes 9 APIs on the APIs.io network, including Cancel Service Order API, Change Request API, events subscription API, and 6 more. Tagged areas include Telecommunications, Canada, Mobile Network Operator, Broadband, and 5G.

The Bell Canada catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Bell Canada’s developer surface includes authentication, sandbox, code examples, getting-started guide, support, documentation, API reference, and 32 more developer resources.

🌐 Visit website 📡 Source on GitHub

48.2/100 developing ▬ flat Agent 31/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

4 APIs

Telecommunications Canada Mobile Network Operator Broadband 5G IoT TM Forum BSS OSS Network APIs CAMARA Open Gateway Identity Verification SIM Swap Enterprise

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 48.2/100 · developing

Contract Quality 10.7 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 5.1 / 15

Operational Transparency 2.1 / 10

Contract Governance 0.4 / 9

Discoverability 4.9 / 8

Regulatory Posture 6.5 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/bell-canada: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Bell Canada Cancel Service Order API

The cancelServiceOrder API from Bell Canada — 2 operation(s) for cancelserviceorder.

Bell Canada Change Request API

The changeRequest API from Bell Canada — 2 operation(s) for changerequest.

Bell Canada events subscription API

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

Bell Canada Logical Resource API

The logicalResource API from Bell Canada — 2 operation(s) for logicalresource.

Bell Canada notification listeners (client side) API

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

Bell Canada Physical Resource API

The physicalResource API from Bell Canada — 2 operation(s) for physicalresource.

Bell Canada Resource API

The Resource API from Bell Canada — 3 operation(s) for resource.

Bell Canada Service Order API

The serviceOrder API from Bell Canada — 2 operation(s) for serviceorder.

Bell Canada Trouble Ticket API

The troubleTicket API from Bell Canada — 2 operation(s) for troubleticket.

Scroll for all 9

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API ChangeManagement

OPEN COLLECTION

Resource Inventory Management

OPEN COLLECTION

API ServiceOrdering

OPEN COLLECTION

Trouble Ticket

OPEN COLLECTION

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Bell Canada Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bell Canada Authentication

apiKey · 2 schemes

SECURITY

Bell Canada Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Bell Canada Agentic Access

74 operations · 60 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

GettingStarted

DeveloperPortal

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 8

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

AgentSkill

AgentSkill

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Scroll for all 8

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Webhooks

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Examples

Examples

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Security

Security

Operate 2

Status, limits, changes, and where to get help

Support

Support

Contact

Contact

Commercial 2

Pricing, plans, and the legal terms of use

Privacy

Privacy

TermsOfService

TermsOfService

Company 3

The organization behind the API

Website

Website

Partners

Partners

Blog

Blog

Other 7

Properties that don't map to a standard resource type

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Products

Company

Scroll for all 7

Source (apis.yml)

aid: bell-canada
url: https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/apis.yml
name: Bell Canada
kind: company
description: 'Bell Canada is Canada''s largest communications company and the principal operating subsidiary of BCE Inc.,
  providing wireless, wireline, internet, television and enterprise network services across Canada, and operating Bell Media
  as the country''s largest broadcaster. As a facilities-based mobile network operator and broadband carrier it sits at the
  connectivity layer of the telecom value chain, and its public API posture reflects that: Bell runs a real developer portal
  at developer.bell.ca whose only published API suite is a set of four TM Forum Open API aligned B2B service management interfaces
  — Trouble Ticket (TMF621), Service Order (TMF641), Resource Inventory (TMF639) and Change Management (TMF655) — for enterprise
  and wholesale partners integrating their ITSM systems with Bell. The Swagger 2.0 definitions and PDF specifications are
  downloadable without a login, but access to the sandbox and to any live endpoint requires a business registration form and
  manual approval; no base URL, no credential scheme and no self-serve key issuance is published, and the documented request
  examples redact the credential as a literal SECURITY_CREDENTIALS placeholder. Bell publishes no first-party CAMARA network
  APIs and runs no Open Gateway portal of its own. Its network APIs reach developers indirectly, through EnStream LP — the
  identity and fraud-signal joint venture Bell Mobility owns with Rogers and TELUS — which announced a partnership with Aduna,
  the Ericsson-and-carrier joint venture, on 27 February 2025 to distribute Canadian Number Verification and SIM Swap signals
  through Aduna''s CAMARA-aligned global channel. Bell is therefore an aggregator-mediated carrier: partner-gated on its own
  surface, reachable by developers only through a third party.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Telecommunications
- Canada
- Mobile Network Operator
- Broadband
- 5G
- IoT
- TM Forum
- BSS
- OSS
- Network APIs
- CAMARA
- Open Gateway
- Identity Verification
- SIM Swap
- Enterprise
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- aid: bell-canada:bell-canada-cancelserviceorder-api
  name: Bell Canada Cancel Service Order API
  description: The cancelServiceOrder API from Bell Canada — 2 operation(s) for cancelserviceorder.
  humanURL: https://developer.bell.ca/troubleticket
  tags: []
  tags_raw:
  - cancelServiceOrder
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-cancelserviceorder-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-changerequest-api
  name: Bell Canada Change Request API
  description: The changeRequest API from Bell Canada — 2 operation(s) for changerequest.
  humanURL: https://developer.bell.ca/troubleticket
  tags: []
  tags_raw:
  - changeRequest
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-changerequest-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-events-subscription-api
  name: Bell Canada events subscription API
  description: The events subscription API from Bell Canada — 2 operation(s) for events subscription.
  humanURL: https://developer.bell.ca/troubleticket
  tags:
  - events subscription
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-events-subscription-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-logicalresource-api
  name: Bell Canada Logical Resource API
  description: The logicalResource API from Bell Canada — 2 operation(s) for logicalresource.
  humanURL: https://developer.bell.ca/troubleticket
  tags: []
  tags_raw:
  - logicalResource
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-logicalresource-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-notification-listeners-client-side-api
  name: Bell Canada notification listeners (client side) API
  description: The notification listeners (client side) API from Bell Canada — 31 operation(s) for notification listeners
    (client side).
  humanURL: https://developer.bell.ca/troubleticket
  tags:
  - notification listeners (client side)
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-notification-listeners-client-side-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-physicalresource-api
  name: Bell Canada Physical Resource API
  description: The physicalResource API from Bell Canada — 2 operation(s) for physicalresource.
  humanURL: https://developer.bell.ca/troubleticket
  tags: []
  tags_raw:
  - physicalResource
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-physicalresource-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-resource-api
  name: Bell Canada Resource API
  description: The Resource API from Bell Canada — 3 operation(s) for resource.
  humanURL: https://developer.bell.ca/troubleticket
  tags:
  - Resource
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-resource-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-serviceorder-api
  name: Bell Canada Service Order API
  description: The serviceOrder API from Bell Canada — 2 operation(s) for serviceorder.
  humanURL: https://developer.bell.ca/troubleticket
  tags: []
  tags_raw:
  - serviceOrder
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-serviceorder-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
- aid: bell-canada:bell-canada-troubleticket-api
  name: Bell Canada Trouble Ticket API
  description: The troubleTicket API from Bell Canada — 2 operation(s) for troubleticket.
  humanURL: https://developer.bell.ca/troubleticket
  tags:
  - Trouble Ticket
  tags_raw:
  - troubleTicket
  properties:
  - type: OpenAPI
    url: openapi/bell-canada-troubleticket-api-openapi.yml
  - type: Documentation
    url: https://developer.bell.ca/troubleticket
  - type: APIReference
    url: https://developer.bell.ca/troubleticket
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Trouble_Ticket_v2_5_af537009fa.pdf
  - type: Documentation
    url: https://developer.bell.ca/serviceorder
  - type: APIReference
    url: https://developer.bell.ca/serviceorder
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Service_Order_v1_4_1_1bdd4073d5.pdf
  - type: Documentation
    url: https://developer.bell.ca/resourceinventory
  - type: APIReference
    url: https://developer.bell.ca/resourceinventory
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Resource_Inventory_v1_6_1_855c08df43.pdf
  - type: Documentation
    url: https://developer.bell.ca/changemanagement
  - type: APIReference
    url: https://developer.bell.ca/changemanagement
  - type: Specification
    url: https://developer.bell.ca/uploads/BELL_Canada_API_Specification_Change_Management_v1_1_1_b54db5b465.pdf
common:
- type: CapabilityMap
  url: capabilities/bell-canada-capability-edges.yml
  name: Bell Canada Business Capability Map
- type: Overlay
  url: overlays/bell-canada-trouble-ticket-api-overlay.yaml
- type: AgentSkill
  url: skills/bell-canada-raise-and-track-trouble-ticket.md
- type: Overlay
  url: overlays/bell-canada-service-order-api-overlay.yaml
- type: AgentSkill
  url: skills/bell-canada-place-and-cancel-service-order.md
- type: Overlay
  url: overlays/bell-canada-resource-inventory-api-overlay.yaml
- type: AgentSkill
  url: skills/bell-canada-query-resource-inventory.md
- type: Overlay
  url: overlays/bell-canada-change-management-api-overlay.yaml
- type: AgentSkill
  url: skills/bell-canada-raise-change-request.md
- type: AgenticAccess
  url: agentic-access/bell-canada-agentic-access.yml
- type: DomainSecurity
  url: security/bell-canada-domain-security.yml
- type: Authentication
  url: authentication/bell-canada-authentication.yml
- type: Conventions
  url: conventions/bell-canada-conventions.yml
- type: ErrorCatalog
  url: errors/bell-canada-problem-types.yml
- type: Lifecycle
  url: lifecycle/bell-canada-lifecycle.yml
- type: Sandbox
  url: sandbox/bell-canada-sandbox.yml
- type: Conformance
  url: conformance/bell-canada-conformance.yml
- type: Webhooks
  url: asyncapi/bell-canada-webhooks.yml
- type: DataModel
  url: data-model/bell-canada-data-model.yml
- type: Examples
  url: examples/bell-canada-examples.yml
- type: X-MCPServerCandidate
  url: mcp/bell-canada-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/bell-canada-llms.txt
- type: GettingStarted
  url: https://developer.bell.ca/faq/apis
- type: Support
  url: https://developer.bell.ca/contact
- type: GitHubOrganization
  url: https://github.com/bellcanada
- type: Website
  url: https://www.bell.ca
- type: DeveloperPortal
  url: https://developer.bell.ca
- type: Documentation
  url: https://developer.bell.ca/overview
- type: APIReference
  url: https://developer.bell.ca/servicemanagement
- type: SignUp
  url: https://developer.bell.ca/register
- type: Contact
  url: https://developer.bell.ca/contact
- type: Partners
  url: https://developer.bell.ca/partners
- type: Blog
  url: https://developer.bell.ca/article
- type: Products
  url: https://developer.bell.ca/product
- type: Privacy
  url: https://aliant.bell.ca/Security_and_privacy/Commitment_to_privacy
- type: TermsOfService
  url: https://aliant.bell.ca/Legal_and_terms
- type: Security
  url: https://support.bell.ca/Billing-and-Accounts/Security_and_privacy
- type: Company
  url: https://www.bce.ca
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/bell-canada"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/bell-canada/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/bell-canada/evidence"

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.

GitHub Google LinkedIn

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