# Rogers Communications

> Canada's largest wireless carrier and, after its 2023 acquisition of Shaw Communications, one of the country's largest cable, internet and media companies. In the API value chain Rogers sits on the network-operator side, not the developer-facing side: it runs no developer portal, publishes no OpenAPI, offers no sandbox and ships no SDKs. Its network capabilities reach developers only through intermediaries.

Generated by the API Evangelist enrichment pipeline on 2026-07-25 from https://github.com/api-evangelist/rogers. Nothing here is fabricated; every claim below was probed or sourced.

## What is real

- The only Rogers-named API surface is **Rogers Control Centre**, its managed IoT/M2M connectivity platform — a white-labelled deployment of Cisco IoT Control Center (formerly Jasper). Rogers lists "Access to applicable REST APIs" and "Access to applicable REST and SOAP APIs" as tier features but documents no endpoints of its own.
- The Rogers tenant console is live at https://rogers.jasper.com/provision (Cisco Control Center login). Access requires a Rogers Business contract plus platform credentials; there is no self-serve signup.
- Authentication is HTTP Basic (username + API key) for REST, a license key for SOAP, and a shared secret for PUSH callbacks. Verified live: the Jasper REST tier answers `WWW-Authenticate: Basic realm="Jasper"`.
- CAMARA-defined capabilities (Number Verification, SIM Swap) reach developers through EnStream — the Bell/Rogers/TELUS identity joint venture — via Aduna, and since 2026-06-30 through Vonage's Canadian network-API launch. Nothing CAMARA is callable, documented or even named on a Rogers-owned domain.

## What is not real

- No developer portal: developer.rogers.com, developers.rogers.com, docs.rogers.com, apis.rogers.com, opengateway.rogers.com and developer.rogers.ca all fail DNS.
- No spec: every OpenAPI/Swagger/AsyncAPI/GraphQL path probed on Rogers hosts returns 404.
- No first-party SDKs, no CLI, no public Postman workspace, no verifiable GitHub organization.
- No /.well-known/ documents of any kind, including security.txt and openid-configuration.
- The legacy Rogers Catalyst developer programme is a dangling redirect: www.rogers.com/developer meta-refreshes to rogerscatalyst.com, a domain Rogers no longer controls.

## APIs

- [Rogers Control Centre IoT APIs](https://www.rogers.com/business/iot/control-centre): managed IoT/M2M connectivity — SIM lifecycle, SIM ordering, rate plans, diagnostics, automation. REST (all tiers) and SOAP (Advantage tier). Endpoint reference published by Cisco, not Rogers.

## Docs

- [Rogers Business IoT](https://www.rogers.com/business/iot)
- [Rogers Control Centre product page](https://www.rogers.com/business/iot/control-centre)
- [Rogers Control Centre tiers and API access (Rogers Business blog)](https://www.rogers.com/business/blog/en/optimize-and-scale-your-iot-solutions-with-rogers-control-centre)
- [Cisco IoT Control Center REST API functions](https://developer.cisco.com/docs/control-center/rest-api-functions/)
- [Cisco IoT Control Center getting started (auth, pagination, limits)](https://developer.cisco.com/docs/control-center/getting-started/)

## Artifacts

- [Authentication profile](authentication/rogers-authentication.yml)
- [API conventions](conventions/rogers-conventions.yml)
- [Error codes](errors/rogers-error-codes.yml)
- [Rate limits](rate-limits/rogers-rate-limits.yml)
- [Plans / tiers](plans/rogers-plans.yml)
- [Lifecycle](lifecycle/rogers-lifecycle.yml)
- [Conformance and distribution channels](conformance/rogers-conformance.yml)
- [Packages (none official)](packages/rogers-packages.yml)
- [Well-known probe results (all 404)](well-known/rogers-well-known.yml)
- [Domain security probe](security/rogers-domain-security.yml)
- [PUSH API / webhook surface](asyncapi/rogers-push-api-webhooks.yml)

## Company

- [Rogers.com](https://www.rogers.com/)
- [About Rogers](https://about.rogers.com/)
- [Network outages / service status](https://www.rogers.com/support/outage)
- [Support](https://www.rogers.com/support)
- [Rogers Business support](https://www.rogers.com/business/support)
- [Terms and conditions](https://www.rogers.com/support/terms)
- [Privacy policy](https://www.rogers.com/support/privacy/rogers-privacy-policy)