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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Bell Canada

Bell Canada Trouble Ticket API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

Bell Canada Trouble Ticket 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 Trouble Ticket. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, https://serverRoot/tmf-api/troubleTicket/v4/.

5 operations 2 paths 18 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.1.1
Server
https://serverRoot/tmf-api/troubleTicket/v4/
Resource Areas
1

Paths & Operations 5

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

troubleTicket 5
GET
/troubleTicket
List or find TroubleTicket objects
listTroubleTicket 6 params → 200400401403405409500
POST
/troubleTicket
Creates a TroubleTicket
createTroubleTicket body → 201202400401403405409422
GET
/troubleTicket/{id}
Retrieves a TroubleTicket by ID
retrieveTroubleTicket 4 params → 200400401403404405409500
PATCH
/troubleTicket/{id}
Updates partially a TroubleTicket
patchTroubleTicket 1 param body → 200204400401403404405409
DELETE
/troubleTicket/{id}
Deletes a TroubleTicket
deleteTroubleTicket 1 param → 204400401403404405409500

Schemas 18

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

AttachmentRefOrValue
An attachment by value or by reference. For AttachmentRefOrValue, the attribute type,schemaLocation and referredType are related to the contained entity and no…
Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
RelatedParty
Related Entity reference. A related party defines party or party role linked to a specific entity.
TroubleTicket_Update
A trouble ticket is a record of an issue that is created, tracked, and managed by a trouble ticket management system Skipped properties: id,href,creationDate,l…
AttachmentRef
Attachment reference. An attachment complements the description of an element (for instance a product) through video, pictures
StatusChange
Holds the status notification reasons and associated date the status changed, populated by the server
ChannelRef
The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..
TroubleTicketStatusType
string
Possible values for the status of the trouble ticket
Attachment
Complements the description of an element (for instance a product) through video, pictures...
RelatedEntity
A reference to an entity, where the type of the entity is not known in advance.
TroubleTicket_Create
A trouble ticket is a record of an issue that is created, tracked, and managed by a trouble ticket management system Skipped properties: id,href
TroubleTicketRelationship
Represents a relationship between trouble Trouble Tickets
EntityRef
Base entityRef schema for use in TMForum Open-APIs
TimePeriod
object
A period of time, either as a deadline (endDateTime only) a startDateTime only, or both
2 properties
Entity
object
Base entity schema for use in TMForum Open-APIs
3 properties
Quantity
object
An amount in a given unit
2 properties
TroubleTicket
A trouble ticket is a record of an issue that is created, tracked, and managed by a trouble ticket management system
Note
Extra information about a given entity

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bell-canada-troubleticket-api-openapi.yml Raw ↑

Other APIs Bell Canada publishes across the network.

Bell Canada Cancel Service Order API
AE Profile APIs.io
Bell Canada Change Request API
AE Profile APIs.io
Bell Canada events subscription API
AE Profile APIs.io
Bell Canada Logical Resource API
AE Profile APIs.io
Bell Canada notification listeners (client side) API
AE Profile APIs.io
Bell Canada Physical Resource API
AE Profile APIs.io
Bell Canada Resource API
AE Profile APIs.io
Bell Canada Service Order API
AE Profile APIs.io
#Trouble Ticket
← Back to B APIs
API Details
ID
bell-canada:bell-canada-troubleticket-api
Server
https://serverRoot/tmf-api/troubleTicket/v4/
Docs
https://developer.bell.ca/troubleticket
Provider
Bell Canada
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=bell-canada-troubleticket-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bell-canada-troubleticket-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Bell Canada Trouble Ticket 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.