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

Optum Medicare Fee Schedule APIs API

The Medicare Fee Schedule APIs API from Optum — 10 operation(s) for medicare fee schedule apis.

Optum Medicare Fee Schedule APIs API is one of 166 APIs that Optum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Medicare Fee Schedule APIs. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, a getting-started guide, authentication docs, a changelog, and API documentation.

This API exposes 10 operations across 10 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version v1.0.

Requests are made against 2 base URLs: /v1/cmscommonms, /v1/optumcommonms.

10 operations 10 paths 1 schemas 10 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0
Base URL
https://apigw.optum.com/medicalnetwork/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Optum Medicare Fee Schedule APIs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 10

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

Medicare Fee Schedule APIs 10
GET
/api/cms/physician/{code}/physician-time
Fetches Physician time for particular CPT or HCPCS code
getPhysicianTime 2 params → 200404500
GET
/api/cms/physician/mpfs/status-codes
Fetches MPFS Status codes
getStatusCodes 1 param → 200404500
GET
/api/cms/physician/mpfs/payment-indicators/{ruletype}
Fetches MPFS payment indicators and its definitions for particular medicare rule type
getPaymentIndicatorList 2 params → 200404500
GET
/api/cms/physician/mpfs/payment-indicator-status/{code}
Fetches payment indicator and status information for CPT or HCPCS codes
fetchPaymentIndicatorAndStatusFees 2 params → 200404500
GET
/api/cms/physician/mpfs/national-physician-relative-file
Fetches MPFS file content particular medicare rule type
getRelativeFile 1 param → 200404500
GET
/api/cms/physician/mpfs/global-days/{code}
Fetches MPFS global days for CPT and HCPCS code
getGlobalDays 2 params → 200400404500
GET
/api/cms/physician/mpfs/fee-schedule/{codetype}/{code}/{carrier}/{locality}
Fetches MPFS fee schedule
fetchMedicareFees 6 params → 200404500
GET
/api/cms/physician/mpfs/fee-schedule/mpfs-reduction-groups/hcpcs/{code}
Fetches MPFS reduction groups applicable for particular code
getHcpcsMedicareReductionGroups 2 params → 200404500
GET
/api/cms/physician/mpfs/fee-schedule/mpfs-reduction-groups/cpt/{code}
Fetches MPFS Reduction Groups applicable for particular code
getCptMedicareReductionGroups 2 params → 200404500
GET
/api/optum/physician/mpfs/locality-fee/{codetype}/{code}/{carrier}/{locality}
Fetches MPFS fee scedule
fetchMedicareLocalityFees 6 params → 200404500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Notification (3 properties). Each schema is shown below with its type and property counts.

Notification
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optum-medicare-fee-schedule-apis-api-openapi.yml Raw ↑

Other APIs Optum publishes across the network.

Optum Real (Medical) API
Optum Interoperability APIs (CMS Patient Access)
Optum Ambulance Fee Schedule APIs API
Optum Anesthesia Fee APIs API
Optum APC Calculator APIs API
Optum APC Cross Codes APIs API
Optum Apip API
Optum Application.wadl API
Optum Attachment API
Optum Attachment Document API
Optum Attachment Status API
Optum Attachment Submission API
Where this information came from

This is an independent, third-party profile of Optum Medicare Fee Schedule APIs 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.