This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
TELUS Corporation is one of Canada's three national facilities-based telecommunications carriers, operating a nationwide mobile network alongside broadband, TV, security, health (TELUS Health) and agriculture (TELUS Agriculture & Consumer Goods) businesses from its Vancouver headquarters. In the API value chain TELUS is a network owner rather than a developer-facing platform: its API Marketplace at api.telus.com sits behind the TELUS Client Identity login, its developers.telus.com "Simplify" portal is an internal/partner surface that refuses anonymous requests, and its IoT Marketplace is a login wall. The one genuinely public developer surface is the TELUS Insights Location API, a geo-intelligence product documented openly on Postman with a live OAuth2-protected gateway, though credentials are issued only through a sales onboarding process. TELUS is a named participant in the CAMARA project and appears in the CAMARA landscape as an operator, but it publishes no first-party CAMARA endpoint — its Number Verification and SIM Swap network APIs reach developers indirectly through EnStream LP, the Bell/Rogers/TELUS identity joint venture, which feeds Aduna and from there CPaaS channels such as Vonage. TELUS is partner-gated and, for network APIs, reachable only through aggregators.
APIs.json: https://raw.githubusercontent.com/api-evangelist/telus/refs/heads/main/apis.yml
- Kind: company
- Home market: Canada
- Tier: Mobile network operator / broadband carrier
- Telecommunications
- Canada
- Mobile Network Operator
- Broadband
- Network APIs
- CAMARA
- Open Gateway
- SIM Swap
- Identity Verification
- Location Intelligence
- IoT
- 5G
- Created: 2026-07-25
- Modified: 2026-07-25
The TELUS Insights Location API exposes de-identified, aggregated geo-intelligence derived from the TELUS mobile network across Canada. Consumers submit asynchronous count jobs — demographic, origin, destination, origin-destination matrix, dwell time, trade area, repeat visitation, total trip, unique devices, home and work — against uploaded shapefile study zones or built-in geofences, then poll a job identifier for results. Documentation is published publicly through Postman; the gateway at location-api.insights.telus.com is live and returns 401 without a bearer token. Access uses OAuth2 client credentials issued through the TELUS Insights Portal after a sales-led onboarding, so the API is documented publicly but is not self-serve.
- Human URL: https://docs.insights.telus.com/
- Base URL:
https://location-api.insights.telus.com/product/insightsRequest/v1
The TELUS Health Collaborative Health Record (CHR) Enterprise API is a GraphQL interface onto the CHR ambulatory-care platform used by Canadian clinics. Its published introspection document describes 505 types, 64 root queries and 49 mutations spanning patients, appointments and availability, encounters, referrals, cases, tasks, group visits, attachments, letters, lab results (including OLIS lab messages), allergy and medication records, health profiles, facilities, providers and work hours. Pagination follows the GraphQL Cursor Connections specification (default 50, maximum 100). Authentication is a consumer-minted RS512 JWT — you generate a 2048-bit RSA key pair, register the public key on an API Consumer inside the CHR account, and sign your own token with a matching iss and a ≤ 900-second expiry. There is no authorization server, no token endpoint and no client secret. A companion Event Notification Service pushes 21 signed webhook topics carrying identifiers only, with no personal or personal-health information in the payload.
- Human URL: https://help.inputhealth.com/en/collections/3317215-chr-enterprise-api
- Schema surface:
https://apidocs.ca.inputhealth.com/enterprise-api(GraphQL Voyager)
- GraphQL SDL
- GraphQL introspection (verbatim)
- Documentation
- API reference
- Getting started / onboarding
- Event notifications
- Changelog
No OpenAPI or Swagger document is published publicly by TELUS, so there is no openapi/ directory in this repository. The Insights documentation points readers at a "Swagger file" that lives behind the Insights Portal login; every anonymous specification path probed returned 404, 401 or an SPA catch-all. There is also no MCP server, no CLI, no API client SDK in any language, no public status page, no SLA, no published deprecation policy, no idempotency contract on either API, and no TELUS-owned security.txt.
The one machine-readable contract TELUS does publish is the CHR GraphQL introspection document above — and it is not on a telus.com domain, which is why the first review round recorded "zero specs harvested."
The TELUS API Marketplace at api.telus.com redirects anonymous requests to the TELUS Client Identity login. developers.telus.com — the internal "Simplify" developer portal — resets anonymous TLS connections. iot.telus.com is an IoT Marketplace login page. opengateway.telus.com, developer.telus.com, apis.telus.com and networkapi.telus.com do not resolve. designsystem.telus.com and tds.telus.com serve expired TLS certificates.
TELUS participates in CAMARA — six TELUS staff are named in camaraproject/Governance/PARTICIPANTS.MD, and TELUS is listed as an Operator in the CAMARA landscape — but it exposes no first-party CAMARA endpoint. Canada's network APIs are aggregated by EnStream LP, the mobile-identity joint venture owned by Bell Mobility, Rogers and TELUS, which partnered with Aduna (the Ericsson-led carrier JV) in February 2025 to publish Number Verification and SIM Swap. In June 2026 Vonage commercially launched SIM Swap Detection and Silent Authentication in Canada over that same path. A developer who wants a TELUS network capability buys it from Vonage or Aduna — never from TELUS.
No evidence was found that TELUS signed the GSMA Open Gateway MoU, and no TM Forum Open API conformance certification was found. CIBA, the backchannel authentication flow CAMARA specifies, does not appear on any TELUS property.
| Artifact | Path |
|---|---|
| GraphQL SDL + introspection (CHR) | graphql/ |
| Postman collection (Insights) | collections/ |
| Authentication profile | authentication/telus-authentication.yml |
| OAuth scopes | scopes/telus-scopes.yml |
| API conventions | conventions/telus-conventions.yml |
| Error catalog | errors/telus-problem-types.yml |
| Rate limits and usage guidance | rate-limits/telus-rate-limits.yml |
| Webhook / event catalog (CHR ENS) | asyncapi/telus-chr-event-notifications.yml |
| Lifecycle and versioning | lifecycle/telus-lifecycle.yml |
| Changelog | changelog/telus-changelog.yml |
| Data model | data-model/telus-data-model.yml |
| Conformance | conformance/telus-conformance.yml |
| Sandbox and test surfaces | sandbox/telus-sandbox.yml |
| Packages | packages/telus-packages.yml |
| Embedded components (UDS) | components/telus-components.yml |
| Agent skills | skills/ |
| llms.txt | llms/telus-llms.txt |
| Well-known discovery probes | well-known/telus-well-known.yml |
| Domain security | security/telus-domain-security.yml |
| Vulnerability disclosure | security/telus-vulnerability-disclosure.yml |