Rogers Communications

Rogers Control Centre IoT APIs

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.

GitHub

Documentation

📖
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/
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/authentication/rogers-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/rogers/refs/heads/main/rate-limits/rogers-rate-limits.yml

Other Resources

🔗
Console
https://rogers.jasper.com/provision
🔗
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
🔗
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

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/rogers-control-centre-iot-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: rogers:rogers-control-centre-iot-api
name: Rogers Control Centre IoT APIs
description: 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.
humanURL: https://www.rogers.com/business/iot/control-centre
baseURL: https://rogers.jasper.com/
tags:
- IoT
- M2M
- Connectivity Management
- SIM LifeCycle
- Canada
tags_raw:
- IoT
- M2M
- Connectivity Management
- SIM Lifecycle
- Canada
properties:
- type: Documentation
  url: https://www.rogers.com/business/iot/control-centre
- type: Documentation
  url: https://www.rogers.com/business/blog/en/optimize-and-scale-your-iot-solutions-with-rogers-control-centre
- type: APIReference
  url: https://developer.cisco.com/docs/control-center/rest-api-functions/
- type: GettingStarted
  url: https://developer.cisco.com/docs/control-center/getting-started/
- type: Console
  url: https://rogers.jasper.com/provision
- type: Authentication
  url: authentication/rogers-authentication.yml
- type: Conventions
  url: conventions/rogers-conventions.yml
- type: ErrorCatalog
  url: errors/rogers-error-codes.yml
- type: RateLimits
  url: rate-limits/rogers-rate-limits.yml
- type: Plans
  url: plans/rogers-plans.yml