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

Bell Canada Cancel Service Order API

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

Bell Canada Cancel Service Order API is one of 9 APIs that Bell Canada publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 4.6.0.

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

3 operations 2 paths 8 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 3

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

cancelServiceOrder 3
GET
/cancelServiceOrder
List or find CancelServiceOrder objects
listCancelServiceOrder 6 params → 200400401403405409500
POST
/cancelServiceOrder
Creates a CancelServiceOrder
createCancelServiceOrder body → 201202400401403405409422
GET
/cancelServiceOrder/{id}
Retrieves a CancelServiceOrder by ID
retrieveCancelServiceOrder 4 params → 200400401403404405409500

Schemas 8

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

Error
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
TaskStateType
string
Possible values for the state of a task
CancelServiceOrder_Create
Request for cancellation an existing Service order Skipped properties: id,href,state,effectiveCancellationDate,completionMessage,errorMessage
EntityRef
Base entityRef schema for use in TMForum Open-APIs
Entity
object
Base entity schema for use in TMForum Open-APIs
3 properties
ErrorMessage
represents an Error
ServiceOrderRef
Service Order reference. Useful to understand the which was the Service order through which the service was instantiated in the service inventory
CancelServiceOrder
Request for cancellation an existing Service order

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Bell Canada publishes across the network.

Bell Canada Change Request API
Bell Canada events subscription API
Bell Canada Logical Resource API
Bell Canada notification listeners (client side) API
Bell Canada Physical Resource API
Bell Canada Resource API
Bell Canada Service Order API
Bell Canada Trouble Ticket API
Where this information came from

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