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
Sun Life Financial Inc. is a Canadian multinational life and health insurer and asset manager headquartered in Toronto, one of the "life trio" that dominates Canada's insurance market alongside Manulife and Great-West Lifeco. Sun Life writes individual life insurance, individual and group health and dental coverage, group benefits, disability and absence management, annuities and retirement products, and runs a large wealth business through Sun Life Global Investments, SLC Management and MFS Investment Management, with operations across Canada, the United States, the United Kingdom, Ireland and Asia. In the United States it is a leading group benefits, stop-loss and dental carrier and owns DentaQuest.
APIs.json: https://raw.githubusercontent.com/api-evangelist/sun-life/refs/heads/main/apis.yml
- Insurance
- Canada
- Life Insurance
- Health Insurance
- Employee Benefits
- Group Benefits
- Dental Insurance
- Disability
- Wealth Management
- Financial Services
- Carrier
- Created: 2026-07-25
- Modified: 2026-07-25
Three, all from DentaQuest, the Sun Life U.S. dental company — not from the Sun Life brand itself. DentaQuest runs a public Azure API Management developer portal at developers.dentaquest.com publishing OpenAPI 3.0.1 for three FHIR R4 APIs released under the CMS Interoperability and Patient Access Final Rule (CMS-9115-F). All three specs are harvested to openapi/.
| API | Base URL | Auth | Paths |
|---|---|---|---|
| FHIR Patient Access | https://api.dentaquest.com/FhirPatientAccess/v1 |
SMART on FHIR (OAuth 2.0 code + PKCE) via Okta CIAM | 31 |
| FHIR Provider Directory | https://api.dentaquest.com/FhirProviderDirectory |
Azure APIM subscription key | 36 |
| FHIR Metadata | https://api.dentaquest.com/fhirmetadata |
anonymous | 1 |
Patient Access instantiates US Core 3.1.1 / 6.1.0 / 7.0.0-ballot and publishes a live SMART configuration with real scopes (patient/*.read, launch/patient, offline_access, openid, fhirUser). Provider Directory conforms to Da Vinci PDex Plan-Net 1.1.0. Both specs list api.deltadentalma.com as a second production server — the same backend serves the Delta Dental of Massachusetts brand. Credentials are not self-serve: a developer questionnaire is reviewed and production credentials are emailed.
Under the Sun Life brand there is still no public API. Probed on 2026-07-25: developer.sunlife.com, developers.sunlife.com, docs.sunlife.com, api.sunlife.com, apis.sunlife.com, gateway.sunlife.com and partners.sunlife.com do not resolve in DNS, and neither do the equivalents under sunlife.ca. The paths /developers, /developer, /partners and /integrations on www.sunlife.com all return HTTP 404, as do /openapi.json, /swagger.json and /api-docs. The www.sunlife.com/api vanity path redirects to the Sun Life U.S. Digital capabilities marketing page.
Sun Life's only named API surface is Sun Life Link, described on its own product page as "our API solution" delivering "real-time data exchanges with the HR platforms you use every day." It is a partner-gated U.S. group-benefits connectivity program, not a developer program: connections are negotiated per client and per platform, and the company's own RFP guidance tells buyers to ask carriers for "a breakdown of pricing per API" and whether APIs are "offered to all clients, or only a subset."
Named platform connections and live capabilities, as published:
| Platform | Capabilities |
|---|---|
| Workday | EOI, Billing, Absence (leave create/update, intermittent leave, return-to-work, leave consolidation); Plan Setup and Enrollment via Workday Wellness listed as Q4 |
| ADP Workforce Now | EOI, Plan Setup, self-bill; Enrollment in early adopter |
| ADP Vantage HCM / Health & Welfare Service Engine / ADP Lyric HCM | EOI, Plan Setup; Enrollment a future enhancement |
| UKG Pro Benefits Administration | EOI |
| PlanSource | EOI |
| Employee Navigator | Plan Setup; EOI a future enhancement |
| bswift | EOI |
Sun Life also states "general connectivity with 150 + other HR platforms."
Of the four insurance API verbs, quote, bind and FNOL are not exposed publicly at all. Issue is present only in partner-gated form as Plan Setup, Enrollment and Evidence of Insurability exchanges. Claims are submitted and tracked through the login-gated Sun Life Connect employer portal and the member account.
No ACORD reference found. No mention of ACORD, AL3, ACORD XML, NGDS, IVANS, agency download, Applied Epic or Vertafore AMS360 appears on any Sun Life page or in either public API whitepaper. As a life/health and group-benefits carrier rather than a P&C carrier distributing through independent agencies, Sun Life sits off the ACORD/IVANS rail entirely. Its connectivity vocabulary is generic — the Connectivity 101 whitepaper frames the choice as EDI batch files versus real-time APIs, and names no standards body, not even LIMRA/LDEx.
Canada has the most fragmented insurance supervision of the major markets: OSFI supervises federally-regulated insurers prudentially while the provinces regulate market conduct through FSRA in Ontario, the AMF in Quebec and their counterparts elsewhere. There is no open-insurance mandate, and Consumer-Driven Banking — Canada's open-banking framework — excludes insurance entirely. Nothing compels a Canadian carrier to publish an API, and Sun Life does not. What pull exists comes from the U.S. group-benefits BenTech ecosystem, and Sun Life answers it with negotiated platform partnerships instead of an open developer program.
- Website
- About Us
- Sun Life Canada
- Sun Life U.S.
- Digital capabilities
- Sun Life Link
- Sun Life Connect
- Sun Life Onboard
- Connectivity education materials
- Sign in
- Canadian advisor community
- Investor relations
- Newsroom
- Careers
- Kin Lane — kin@apievangelist.com