# Rogers Control Centre IoT APIs

**Canonical:** https://apis.io/apis/rogers/rogers-control-centre-iot-api/  
**Provider:** Rogers Communications — https://apis.io/providers/rogers/  
**Base URL:** https://rogers.jasper.com/  
**Documentation:** https://www.rogers.com/business/iot/control-centre

Rogers Control Centre IoT APIs is published by [Rogers Communications](https://apis.io/providers/rogers/) on the [APIs.io](https://apis.io/) network. Tagged areas include IoT, M2M, Connectivity Management, SIM Lifecycle, and Canada. The published artifact set on APIs.io includes API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

Rogers Control Centre is Rogers' managed IoT and M2M connectivity management platform, a white-labelled deployment of Cisco IoT Control Center (formerly Jasper). Rogers' own product pages list "Access to applicable REST APIs" and "Access to applicable REST and SOAP APIs" as tier features, so the API surface is real and named by Rogers — but Rogers publishes no endpoint reference, no OpenAPI, and no sandbox of its own. The underlying REST, SOAP, and PUSH API functions are documented by Cisco on Cisco DevNet, and a live Rogers tenant requires an existing Rogers Business contract plus platform credentials. Authentication on the Cisco platform is an API key for REST and a license key for SOAP, with a shared secret used to validate incoming PUSH callbacks. Access is customer-gated; there is no self-serve signup.

## Machine-readable artifacts (11)

- **Documentation** — https://www.rogers.com/business/iot/control-centre
- **Documentation** — https://www.rogers.com/business/blog/en/optimize-and-scale-your-iot-solutions-with-rogers-control-centre
- **APIReference** — https://developer.cisco.com/docs/control-center/rest-api-functions/
- **GettingStarted** — https://developer.cisco.com/docs/control-center/getting-started/
- **Console** — https://rogers.jasper.com/provision
- **Authentication** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/authentication/rogers-authentication.yml
- **Conventions** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/conventions/rogers-conventions.yml
- **ErrorCatalog** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/errors/rogers-error-codes.yml
- **RateLimits** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/rate-limits/rogers-rate-limits.yml
- **Plans** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/plans/rogers-plans.yml
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/apis.yml

## Tags

IoT, M2M, Connectivity Management, SIM Lifecycle, Canada

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/rogers/rogers-control-centre-iot-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/rogers/.