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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Veterans Affairs

Veterans Affairs Medical Records API

The Medical Records API from Veterans Affairs — 30 operation(s) for medical records.

Documentation Provider Profile APIs.io OpenAPI GitHub

Veterans Affairs Medical Records API is one of 25 APIs that Veterans Affairs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Medical Records. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 30 operations across 30 paths. It is described by OpenAPI 3.0.0, at version v0.

Requests are made against 2 base URLs: https://sandbox-api.va.gov/services/appeals/appealable-issues/{version}, https://api.va.gov/services/appeals/appealable-issues/{version}.

30 operations 30 paths 0 schemas 30 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v0
Base URL
https://api.va.gov/services/benefits-intake/v2
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0
Contact
developer.va.gov
Resource Areas
1

Authentication & Security 3

Veterans Affairs Medical Records API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer_token). It supports OAuth 2.0 (productionOauth) using the authorizationCode and clientCredentials flows, exposing 6 scopes. It supports OAuth 2.0 (sandboxOauth) using the authorizationCode and clientCredentials flows, exposing 6 scopes.

  • productionOauth — The authentication model for the Appealable Issues API uses OAuth 2.0/OpenID Connect. The following authorization models are supported: [Authorization code flo…
  • sandboxOauth — The authentication model for the Appealable Issues API uses OAuth 2.0/OpenID Connect. The following authorization models are supported: [Authorization code flo…

Paths & Operations 30

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

Medical Records 30
GET
/v1/medical_records/allergies
/v1/medicalrecords/allergies
list_allergies → 200401403
GET
/v1/medical_records/allergies/{id}
/v1/medicalrecords/allergies/{id}
get_allergy → 200401403
GET
/v1/medical_records/bbmi_notification/status
/v1/medicalrecords/bbminotification/status
bbmi_notification_status → 200401403
GET
/v1/medical_records/ccd/generate
/v1/medicalrecords/ccd/generate
generate_ccd → 200401403
GET
/v1/medical_records/ccd/download.{format}
Download Continuity of Care Document (CCD)
download_ccd 2 params → 200401403
GET
/v1/medical_records/clinical_notes
/v1/medicalrecords/clinicalnotes
list_clinical_notes → 200401403
GET
/v1/medical_records/clinical_notes/{id}
/v1/medicalrecords/clinicalnotes/{id}
get_clinical_note → 200401403
GET
/v1/medical_records/conditions
/v1/medicalrecords/conditions
list_conditions → 200401403
GET
/v1/medical_records/conditions/{id}
/v1/medicalrecords/conditions/{id}
get_condition → 200401403
GET
/v1/medical_records/imaging
/v1/medicalrecords/imaging
list_imaging_studies → 200401403
GET
/v1/medical_records/imaging/status
/v1/medicalrecords/imaging
list_study_job_statuses → 200401403
GET
/v1/medical_records/imaging/{studyId}/dicom
/v1/medicalrecords/imaging/{studyId}/dicom
download_dicom 1 param → 200401403
GET
/v1/medical_records/imaging/{studyId}/images/{seriesId}/{imageId}
/v1/medicalrecords/imaging/{studyId}/images/{seriesId}/{imageId}
download_image 3 params → 200401403
GET
/v1/medical_records/imaging/{studyId}/request
/v1/medicalrecords/imaging/{studyId}/request
request_study → 200400401403404
GET
/v1/medical_records/imaging/{studyId}/images
/v1/medicalrecords/imaging/{studyId}/images
list_images → 200400401403404
GET
/v1/medical_records/labs_and_tests
/v1/medicalrecords/labsandtests
list_labs_and_tests → 200401403
GET
/v1/medical_records/labs_and_tests/{id}
/v1/medicalrecords/labsandtests/{id}
get_labs_and_tests_diagrep → 200401403
GET
/v1/medical_records/military_service
/v1/medicalrecords/militaryservice
get_military_service → 200401403
GET
/v1/medical_records/patient
/v1/medicalrecords/patient
get_patient → 200401403
GET
/v1/medical_records/patient/demographic
/v1/medicalrecords/patient/demographic
get_patient_demographic → 200401403
GET
/v1/medical_records/radiology
/v1/medicalrecords/radiology
get_mhv_radiology → 200401403
GET
/v1/medical_records/self_entered
/v1/medicalrecords/selfentered
get_patient → 200401403
GET
/v1/medical_records/session
/v1/medicalrecords/session
post_session → 204401403
GET
/v1/medical_records/session/status
/v1/medicalrecords/session/status
get_session_status → 200401403
GET
/v1/medical_records/vaccines
/v1/medicalrecords/vaccines
list_vaccines → 200401403
GET
/v1/medical_records/vaccines/{id}
/v1/medicalrecords/vaccines/{id}
get_vaccine → 200401403
GET
/v1/medical_records/vitals
/v1/medicalrecords/vitals
list_vitals → 200401403
GET
/v1/medical_records/vitals/{id}
/v1/medicalrecords/vitals/{id}
get_vitals → 200401403
GET
/v2/medical_records/clinical_notes
/v2/medicalrecords/clinicalnotes
listClinicalNotesV2 3 params → 200400401403502
GET
/v2/medical_records/clinical_notes/{id}
/v2/medicalrecords/clinicalnotes/{id}
getClinicalNoteV2 3 params → 200401403400404502

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

va-medical-records-api-openapi.yml Raw ↑

Other APIs Veterans Affairs publishes across the network.

Patient Health API (FHIR)
AE Profile APIs.io
Health Care Costs and Coverage API (FHIR)
AE Profile APIs.io
Appeals Status API
AE Profile APIs.io
Decision Reviews API
AE Profile APIs.io
VA Facilities API
AE Profile APIs.io
VA Forms API
AE Profile APIs.io
Veteran Verification API
AE Profile APIs.io
Direct Deposit Management API
AE Profile APIs.io
VA Letter Generator API
AE Profile APIs.io
Benefits Reference Data API
AE Profile APIs.io
Veterans Affairs Appealable Issues API
AE Profile APIs.io
Veterans Affairs Appeals Status API
AE Profile APIs.io
#Medical Records
← Back to V APIs
API Details
ID
va:va-medical-records-api
Base URL
https://api.va.gov/services/benefits-intake/v2
Docs
https://developer.va.gov/explore/api/benefits-intake
Provider
Veterans Affairs
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=va-medical-records-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/va-medical-records-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Veterans Affairs Medical Records 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.