How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

CMS — Centers for Medicare & Medicaid Services Auth API

The Auth API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for auth.

CMS — Centers for Medicare & Medicaid Services Auth API is one of 25 APIs that CMS — Centers for Medicare & Medicaid Services publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

This API exposes 2 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://api.bluebutton.cms.gov/v2/fhir, https://sandbox.bluebutton.cms.gov/v2/fhir, https://api.dpc.cms.gov/api/v1, https://sandbox.dpc.cms.gov/api/v1.

2 operations 2 paths 0 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.bluebutton.cms.gov/v2/fhir
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

CMS — Centers for Medicare & Medicaid Services Auth API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 4 scopes. It accepts HTTP bearer tokens (JWT) (BearerAuth).

  • BearerAuth — DPC uses asymmetric SMART Backend Services authentication.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Auth 2
GET
/userinfo
Get Beneficiary User Info
getUserinfo → 200
POST
/Token
Create Client Token
createToken → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cms-gov-auth-api-openapi.yml Raw ↑

Other APIs CMS — Centers for Medicare & Medicaid Services publishes across the network.

CMS — Centers for Medicare & Medicaid Services Articles API
CMS — Centers for Medicare & Medicaid Services Benchmarks API
CMS — Centers for Medicare & Medicaid Services Bulk Export API
CMS — Centers for Medicare & Medicaid Services Catalog API
CMS — Centers for Medicare & Medicaid Services Coverage API
CMS — Centers for Medicare & Medicaid Services Data API
CMS — Centers for Medicare & Medicaid Services Drugs API
CMS — Centers for Medicare & Medicaid Services Eligibility API
CMS — Centers for Medicare & Medicaid Services ExplanationOfBenefit API
CMS — Centers for Medicare & Medicaid Services Geography API
CMS — Centers for Medicare & Medicaid Services Group API
CMS — Centers for Medicare & Medicaid Services Issuers API
Where this information came from

This is an independent, third-party profile of CMS — Centers for Medicare & Medicaid Services Auth API, 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.