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

Bell's implementation of the TM Forum TMF621 Trouble Ticket Open API (Bell version v2.5, TMF621 v4.1.1), letting an enterprise or wholesale partner create, patch, retrieve and list trouble tickets against Bell services from their own ITSM or fault management system. Includes the TM Forum hub/listener notification pattern for ticket create, attribute-value-change, status-change, delete, resolved and information-required events.

Documentation Provider Profile APIs.io OpenAPI GitHub

Bell Canada Trouble Ticket API is one of 4 APIs that Bell Canada publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Trouble Ticket, Service Assurance, TM Forum, TMF621, and B2B. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 13 operations across 10 paths, organized into 3 resource areas, and defines 88 schemas. It is described by OpenAPI 2.0, at version 4.1.1.

13 operations 10 paths 88 schemas 2 DELETE2 GET1 PATCH8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
4.1.1
Resource Areas
3

Paths & Operations 13

Across 10 paths, the API surfaces 13 operations — 2 DELETE, 2 GET, 1 PATCH, 8 POST. They span 3 resource areas: troubleTicket, events subscription, notification listeners (client side). 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 1 param → 201202400401403405409422
GET
/troubleTicket/{id}
Retrieves a TroubleTicket by ID
retrieveTroubleTicket 4 params → 200400401403404405409500
PATCH
/troubleTicket/{id}
Updates partially a TroubleTicket
patchTroubleTicket 2 params → 200204400401403404405409
DELETE
/troubleTicket/{id}
Deletes a TroubleTicket
deleteTroubleTicket 1 param → 204400401403404405409500
events subscription 2
POST
/hub
Register a listener
registerListener 1 param → 201400401403404405409500
DELETE
/hub/{id}
Unregister a listener
unregisterListener 1 param → 204400401403404405500
notification listeners (client side) 6
POST
/listener/troubleTicketCreateEvent
Client listener for entity TroubleTicketCreateEvent
listenToTroubleTicketCreateEvent 1 param → 201400401403404405409500
POST
/listener/troubleTicketAttributeValueChangeEvent
Client listener for entity TroubleTicketAttributeValueChangeEvent
listenToTroubleTicketAttributeValueChangeEvent 1 param → 201400401403404405409500
POST
/listener/troubleTicketStatusChangeEvent
Client listener for entity TroubleTicketStatusChangeEvent
listenToTroubleTicketStatusChangeEvent 1 param → 201400401403404405409500
POST
/listener/troubleTicketDeleteEvent
Client listener for entity TroubleTicketDeleteEvent
listenToTroubleTicketDeleteEvent 1 param → 201400401403404405409500
POST
/listener/troubleTicketResolvedEvent
Client listener for entity TroubleTicketResolvedEvent
listenToTroubleTicketResolvedEvent 1 param → 201400401403404405409500
POST
/listener/troubleTicketInformationRequiredEvent
Client listener for entity TroubleTicketInformationRequiredEvent
listenToTroubleTicketInformationRequiredEvent 1 param → 201400401403404405409500

Schemas 88

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

Attachment
Complements the description of an element (for instance a product) through video, pictures...
AttachmentRef
Attachment reference. An attachment complements the description of an element (for instance a product) through video, pictures
AttachmentRefOrValue
An attachment by value or by reference. For AttachmentRefOrValue, the attribute type,schemaLocation and referredType are related to the contained entity and no…
ChannelRef
The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..
EntityRef
Base entityRef schema for use in TMForum Open-APIs
Note
Extra information about a given entity
Quantity
object
An amount in a given unit
2 properties
RelatedEntity
A reference to an entity, where the type of the entity is not known in advance.
RelatedParty
Related Entity reference. A related party defines party or party role linked to a specific entity.
StatusChange
Holds the status notification reasons and associated date the status changed, populated by the server
TimePeriod
object
A period of time, either as a deadline (endDateTime only) a startDateTime only, or both
2 properties
TroubleTicket
A trouble ticket is a record of an issue that is created, tracked, and managed by a trouble ticket management system
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
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…
TroubleTicketRelationship
Represents a relationship between trouble Trouble Tickets
TroubleTicketStatusType
string
Possible values for the status of the trouble ticket
EventSubscription
object
Sets the communication endpoint address the service instance must use to deliver notification information
3 properties 2 required
EventSubscriptionInput
object
Sets the communication endpoint address the service instance must use to deliver notification information
2 properties 1 required
TroubleTicketCreateEvent
The notification data structure
TroubleTicketCreateEventPayload
object
The event data structure
1 property
TroubleTicketAttributeValueChangeEvent
The notification data structure
TroubleTicketAttributeValueChangeEventPayload
object
The event data structure
1 property
TroubleTicketStatusChangeEvent
The notification data structure
TroubleTicketStatusChangeEventPayload
object
The event data structure
1 property
TroubleTicketDeleteEvent
The notification data structure
TroubleTicketDeleteEventPayload
object
The event data structure
1 property
TroubleTicketResolvedEvent
The notification data structure
TroubleTicketResolvedEventPayload
object
The event data structure
1 property
TroubleTicketInformationRequiredEvent
The notification data structure
TroubleTicketInformationRequiredEventPayload
object
The event data structure
1 property
Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
BellErrorRepresentation
Bell specialized version of the TMF Error. Used to store the native error representation
BellTroubleTicket
Bell version of the TMF TroubleTicket
BellTroubleTicket_Create
Bell version of the TMF TroubleTicket
BellTroubleTicket_Update
Bell version of the TMF TroubleTicket
BellTroubleTicketUrgency
string
Urgency allowed for TMF Trouble Tickets
BellTroubleTicketRelationship
BellTroubleTicketRelationshipWithValue
BellTroubleTicketResolutionInfo
The purpose of this entity is to bound together and summarize useful information about the corrective actions taken to solve the ticket.
BellActivityRefOrValue
The purpose of this entity is to bound together and summarize useful information about the corrective actions taken to solve the ticket.
BellActivityRef
The purpose of this entity is to bound together and summarize useful information about the corrective actions taken to solve the ticket.
BellActivity
The purpose of this entity is to bound together and summarize useful information about the corrective actions taken to solve the ticket.
BellNote
Bell specialized version of the TMF Note. Used to store comments on different entities
BellRelatedPartyWithValue
Related Entity reference embedding the party itself (value of the refOrValue pattern)
Party
Generic Party structure used to define commonalities between sub concepts of Individual and Organization.
Individual
Individual represents a single human being (a man, woman or child). The individual can be a customer, an employee or any other person that the organization nee…
BellIndividual
A Bell extension to an Individual
Organization
Organization represents a group of people identified by shared interests or purpose. Examples include business, department and enterprise. Because of the compl…
BellOrganization
A Bell extension to an Organization
ContactMedium
Indicates the contact medium that could be used to contact the party.
ExternalReference
External reference of the individual or reference in other system
LanguageAbility
Ability of an individual to understand or converse in a language.
MediumCharacteristic
Describes the contact medium characteristics that could be used to contact a party (an individual or an organization)
Skill
Skills evaluated for an individual with a level and possibly with a limited validity when an obsolescence is defined (Ex: the first-aid certificate first level…
RelatedPlaceRefOrValue
Related Entity reference. A related place defines a place described by reference or by value linked to a specific entity. The polymorphic attributes @type, @sc…
GeographicAddress
Structured textual way of describing how to find a Property in an urban area (country properties are often defined differently). Note : Address corresponds to…
GeographicLocationRefOrValue
A GeographicLocation is a pure-virtual super-class to the GeoJSON-aligned geometries of Point (addresses and locations), MultiPoint, LineString (streets, highw…
GeographicLocationRef
GeographicLocation
A GeographicLocation is a pure-virtual super-class to the GeoJSON-aligned geometries of Point (addresses and locations), MultiPoint, LineString (streets, highw…
GeographicSubAddress
Representation of a GeographicSubAddress It is used for addressing within a property in an urban area (country properties are often defined differently). It ma…
Place
Place reference. Place defines the places where the products are sold or delivered.
BellGeographicAddress
A custom Geographic Address to add addressLines.
BellOnSiteSubAddress
A custom SubAddress. Note: type, externalId, sourceSystemId are deprecated.
GeographicSite
GeographicSiteRelationship
PlaceRef
Place reference. PlaceRef defines the placeRefs where the products are sold or delivered.
PlaceRefOrValue
A place described by reference or by value linked to a specific entity. The polymorphic attributes @type, @schemaLocation & @referredType are related to the pl…
CalendarPeriod
HourPeriod
BellGeographicSite
A custom Geographic Site.
Characteristic
Describes a given characteristic of an object or entity through a name/value pair.
StringCharacteristic
Standard TMF string characteristic. Describes a given characteristic of an object or entity through a name/value pair.
BooleanCharacteristic
Standard TMF boolean characteristic. Describes a given characteristic of an object or entity through a name/value pair.
FloatCharacteristic
Standard TMF float characteristic. Describes a given characteristic of an object or entity through a name/value pair.
IntegerCharacteristic
Standard TMF integer characteristic. Describes a given characteristic of an object or entity through a name/value pair.
DateTimeCharacteristic
Standard TMF datetime characteristic. Describes a given characteristic of an object or entity through a name/value pair.
ObjectCharacteristic
Standard TMF object characteristic. Describes a given characteristic of an object or entity through a name/value pair.
ObjectArrayCharacteristic
Standard TMF objectarray characteristic. Describes a given characteristic of an object or entity through a name/value pair.
Entity
object
Base entity schema for use in TMForum Open-APIs
3 properties
Event
Event with common fields. This is an abstract base definition for all events that are produced by TMF APIs. It must be used as a template for specific events.…
CommunicationMessage
Communication message means a notification approach in the format of a message which can be dispatched (sent) to the certain user by the system with the conten…
CommunicationMessageStateType
string
Communication message state type
BellCommunicationMessage
Receiver
Receivers of the communication message.
BellReceiver
Sender
Sender of the communication message.
CommunicationMessageRefOrValue
object
A communication message by value or by reference.
5 properties
CommunicationMessageRef
CommunicationMessage reference. Communication message means a notification approach in the format of a message which can be dispatched (sent) to the certain us…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bell-canada-trouble-ticket-api-openapi.json Raw ↑

Other APIs Bell Canada publishes across the network.

Bell Canada Service Order API
AE Profile APIs.io
Bell Canada Resource Inventory Management API
AE Profile APIs.io
Bell Canada Change Management API
AE Profile APIs.io
#Trouble Ticket#Service Assurance#TM Forum#TMF621#B2B
← Back to B APIs
API Details
ID
bell-canada:bell-canada-trouble-ticket-api
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-trouble-ticket-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bell-canada-trouble-ticket-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.