This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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.
APIs.json: https://raw.githubusercontent.com/api-evangelist/bell-canada/refs/heads/main/apis.yml
- 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
Bell runs a real developer portal at developer.bell.ca (HTTP 200, confirmed 2026-07-25). It is better than a marketing landing page and short of a self-serve developer platform:
- Documentation is public. Four API reference pages with operation tables, curl and Python examples, downloadable Swagger 2.0 JSON, and downloadable PDF specifications — all reachable anonymously, no login wall.
- Access is not. There is no self-serve signup, no key issuance, no console, no published base URL (every spec declares the host as the literal placeholder
serverRoot) and no published credential scheme (examples redact it asSECURITY_CREDENTIALS). Credentials come from submitting a business registration form that Bell reviews manually.
The entire published surface is BSS/OSS B2B service management aligned to TM Forum Open APIs. There is no consumer API, no messaging or voice API, no documented IoT connectivity management API, and no 5G/MEC API despite the portal's 5G and edge computing marketing.
TM Forum TMF621 v4.1.1 (Bell v2.5). Create, patch, retrieve and list trouble tickets against Bell services from a partner ITSM or fault management system.
- Human URL: https://developer.bell.ca/troubleticket
- Documentation
- API Reference
- OpenAPI — Swagger 2.0
- Specification (PDF)
TM Forum TMF641 v4.6 (Bell v1.4). Place, amend, cancel and track service requests with Bell over a B2B integration.
- Human URL: https://developer.bell.ca/serviceorder
- Documentation
- API Reference
- OpenAPI — Swagger 2.0
- Specification (PDF)
TM Forum TMF639 v4.1 (Bell v1.6). Query and maintain an inventory view of the logical and physical Bell resources supporting a partner's services.
- Human URL: https://developer.bell.ca/resourceinventory
- Documentation
- API Reference
- OpenAPI — Swagger 2.0
- Specification (PDF)
TM Forum TMF655 v4.2 (Bell v1.1). Raise, update, retrieve and list change requests against Bell services with guaranteed message delivery.
- Human URL: https://developer.bell.ca/changemanagement
- Documentation
- API Reference
- OpenAPI — Swagger 2.0
- Specification (PDF)
All four APIs implement the TM Forum hub/listener notification pattern — POST /hub registers a callback URL, DELETE /hub/{id} removes it, and a POST /listener/{event} contract exists per event type (create, attribute value change, state/status change, delete, plus resolved, milestone, jeopardy, approval-required, information-required and failure variants). No AsyncAPI document is published.
Bell publishes no first-party CAMARA network APIs. opengateway.bell.ca, developers.opengateway.bell.ca, developers.bell.ca and docs.bell.ca do not resolve; www.bell.ca/opengateway returns 404.
Bell's network capabilities reach developers through an aggregator instead. EnStream LP — the telco identity and fraud-signal joint venture owned by Bell Mobility, Rogers Communications and TELUS Communications — announced a partnership with Aduna (the Ericsson-and-carrier joint venture) on 27 February 2025 to bring Canadian Number Verification and SIM Swap network signals into Aduna's CAMARA-aligned global distribution platform. That is a real, named, dated commercial channel — not a press release with nothing behind it — but the callable surface, the documentation and the developer relationship belong to EnStream and Aduna, not to Bell.
GSMA's Open Gateway supporter pages returned HTTP 403 to anonymous fetches on the review date, so Bell's membership could not be confirmed from a primary source. Bell makes no Open Gateway claim of its own. The 2012 GSMA OneAPI Gateway launched with Bell Mobility, Rogers and TELUS is a different, much older programme and should not be read as Open Gateway participation.
The sector finding, plainly: Bell owns the network; an aggregator owns the developer.