Cigna
Cigna Healthcare is a leading global health services company offering medical, dental, behavioral, and pharmacy plans for individuals, families, and employers. The Cigna Developer Portal exposes CMS-mandated FHIR APIs for Patient Access, Provider Directory, Drug Formulary, and Provider Access, along with member and provider service APIs that enable third-party applications, electronic health record systems, and partners to access member health data with consent and look up Cigna network providers and formulary information.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Cigna the way a machine reads it — 63 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cigna scores 37.1/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Cigna's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cigna/"
title="Cigna on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cigna.svg"
alt="Cigna Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/cigna/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cigna/"
title="Cigna on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cigna/card.svg"
alt="Cigna Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Cigna
Each block below is one kind of artifact we hold for Cigna. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cigna Bulk Data API
The Bulk Data API from Cigna — 1 operation(s) for bulk data.
Cigna Condition API
The Condition API from Cigna — 1 operation(s) for condition.
Cigna Coverage API
The Coverage API from Cigna — 1 operation(s) for coverage.
Cigna Encounter API
The Encounter API from Cigna — 1 operation(s) for encounter.
Cigna ExplanationOfBenefit API
The ExplanationOfBenefit API from Cigna — 1 operation(s) for explanationofbenefit.
Cigna HealthcareService API
The HealthcareService API from Cigna — 1 operation(s) for healthcareservice.
Cigna InsurancePlan API
The InsurancePlan API from Cigna — 2 operation(s) for insuranceplan.
Cigna Location API
The Location API from Cigna — 1 operation(s) for location.
Cigna MedicationKnowledge API
The MedicationKnowledge API from Cigna — 1 operation(s) for medicationknowledge.
Cigna MedicationRequest API
The MedicationRequest API from Cigna — 1 operation(s) for medicationrequest.
Cigna Observation API
The Observation API from Cigna — 1 operation(s) for observation.
Cigna Organization API
The Organization API from Cigna — 1 operation(s) for organization.
Cigna Patient API
The Patient API from Cigna — 4 operation(s) for patient.
Cigna Practitioner API
The Practitioner API from Cigna — 2 operation(s) for practitioner.
Cigna PractitionerRole API
The PractitionerRole API from Cigna — 1 operation(s) for practitionerrole.
Scroll within the panel for all 15 ·
Postman Collections 15
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 15 ·
Open Collections 20
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCigna Drug Formulary Bulk Data API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Condition API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Coverage API
OPEN COLLECTIONCigna Drug Formulary API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Encounter API
OPEN COLLECTIONCigna Drug Formulary Bulk Data ExplanationOfBenefit API
OPEN COLLECTIONCigna Drug Formulary Bulk Data HealthcareService API
OPEN COLLECTIONCigna Drug Formulary Bulk Data InsurancePlan API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Location API
OPEN COLLECTIONCigna Drug Formulary Bulk Data MedicationKnowledge API
OPEN COLLECTIONCigna Drug Formulary Bulk Data MedicationRequest API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Observation API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Organization API
OPEN COLLECTIONCigna Patient Access API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Patient API
OPEN COLLECTIONCigna Drug Formulary Bulk Data Practitioner API
OPEN COLLECTIONCigna Drug Formulary Bulk Data PractitionerRole API
OPEN COLLECTIONCigna Provider Access API
OPEN COLLECTIONCigna Provider Directory API
OPEN COLLECTIONScroll within the panel for all 20 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Cigna GraphQL Schema
This document describes a conceptual GraphQL schema for Cigna Healthcare, one of the largest global health services companies. Cigna's Developer Portal exposes CMS-mandated FHIR...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Cigna Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Cigna Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Cigna Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cigna Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Cigna API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CignaPatient
JSON SCHEMASecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Cigna — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cigna · machine-readable index on apis.io
This is an independent, third-party profile of Cigna, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put 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.