Once you have gained access to our Application Programming Interfaces (APIs), you will receive an email including the API endpoint and credentials. You may use these details to connect to our APIs and submit requests using the technology of your choice (see our API documentation for more detail on how to connect to each API). Once you have tried our APIs and have decided to take the next step, please reach out to our support team with your request.
The APIs enable customer servicing use cases for domains such as Service Assurance, Change Management, Service Provisioning, and the Internet of Things.
End-To-End Customer Journey
Bell suite of APIs is REST based and technology agnostic. Some APIs are based on the TMForum OpenAPI reference model (Click here to visit TMF site) , thus implementing industry strength design patterns to allow simple and coherent management of any given service, and enable a rapid integration.
| REST API Operations Supported | |
| GET/Resource | GET must be used to retrieve a representation of a resource or multiple resources |
| POST Resource | POST must be used to create a new resource |
| PATCH Resource | PATCH must be used to partially update a resource |
| DELETE Resource | DELETE must be used to remove a resource |
| Notification design pattern | Usage of the Publish subscribe pattern so notifications are pushed to a listener in near real-time Hub and notification event filtering |
| Asynchronous Operations design pattern | In some use cases the modification of an attribute or a creation of a record may result in the execution of a long running transaction TransactionMonitor resource is returned so that the execution of the operation can be monitored via the GET operation |
Notification Pattern
Our REST APIs suite is technology and vendor agnostic.
We support both Push and Pull mode communication. However, we favor the Push mode through our notification model.
Some APIs only have Sandbox access. Some other APIs only have Production access. The rest will have access to both environments. Please visit the API details pages of each API for more information.
Once you have reviewed our API documentation and are ready to begin, follow the link below to register and gain access to the Sandbox.
The data in Sandbox environment is fake but will follow the same structure as the data in the production environment.
Security is maintained at all layers of the integration. Bell supports TLSv1.2, 256 bit SHA2 encryption and SSL with proactive monitoring of inbound and outbound traffic. Please ensure you do not submit private data via the Sandbox API.
On the Bell developer API portal, one needs to register to get access to the API. The API can only be accessed using API keys (credentials). After registration, requests will be assessed and validated by a Bell administrator. The Bell administrator will get in touch with the requestor and send a user ID, API end point and other details via email after verification. Using these credentials and API end point, the API can now be accessed.
In our current APIs suite version, connectivity services, managed services and services related to Internet of Things are supported.
*Exceptions and conditions may apply
There is no cost associated with accessing and using the APIs in the sandbox environment. The cost associated to the APIs in production will depend on the individual contract.
Granting access to production environment may or may not require going through an API onboarding project and will require contactual discussions. Please contact your Bell representative for more details.
1. Source: Frost & Sullivan 5G and Edge Computing-Cloud Workloads Shifting to the Edge, Forecast to 2024 - K540-65, August 2020.
Back to top