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
Va

Veterans Affairs Supplemental Claims API

The Supplemental Claims API from Veterans Affairs — 15 operation(s) for supplemental claims.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 15 operations across 15 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://sandbox-api.va.gov/services/appeals/{version}/decision_reviews, https://api.va.gov/services/appeals/{version}/decision_reviews, https://sandbox-api.va.gov/services/appeals/supplemental-claims/{version}, https://api.va.gov/services/appeals/supplemental-claims/{version}.

15 operations 15 paths 33 schemas 7 GET6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 4

Veterans Affairs Supplemental Claims API declares 4 security schemes for authenticating requests. An API key is passed in the header as apikey (apikey). It accepts HTTP bearer tokens (JWT) (bearer_token). It supports OAuth 2.0 (productionOauth) using the authorizationCode and clientCredentials flows, exposing 12 scopes. It supports OAuth 2.0 (sandboxOauth) using the authorizationCode and clientCredentials flows, exposing 12 scopes.

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

Paths & Operations 15

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

Supplemental Claims 15
POST
/supplemental_claims
Creates a new Supplemental Claim
createSc 15 params body → 200422500
GET
/supplemental_claims/{uuid}
Shows a specific Supplemental Claim. (a.k.a. the Show endpoint)
showSc 1 param → 200404500
GET
/supplemental_claims/schema
Gets the Supplemental Claims JSON Schema
scSchema → 200500
POST
/supplemental_claims/validate
Validates a POST request body against the JSON schema
scValidate 15 params body → 200422500
POST
/supplemental_claims/evidence_submissions
Get a location for subsequent evidence submission document upload PUT request
postSupplementalClaimEvidenceSubmission 2 params → 202400404422500
PUT
/sc_upload_path
Accepts Supplemental Claim Evidence Submission document upload
putSupplementalClaimEvidenceSubmission 1 param → 200400500
GET
/supplemental_claims/evidence_submissions/{uuid}
Returns all of the data associated with a specific Supplemental Claim Evidence…
getSupplementalClaimEvidenceSubmission 1 param → 200404500
POST
/forms/200995
Creates a new Supplemental Claim
postForms200995 body → 201400403422500
GET
/forms/200995/{id}
Show a specific Supplemental Claim
getForms200995ById 1 param → 200403404500
GET
/forms/200995/{id}/download
Download a watermarked copy of a submitted Supplemental Claim
downloadSc 2 params → 200400403404410422500
GET
/schemas/{schema_type}
Gets the Supplemental Claims JSON Schema
getSchemasBySchemaType 1 param → 200404500
POST
/forms/200995/validate
Validates a POST request body against the JSON schema
postForms200995Validate body → 200422500
POST
/evidence-submissions
Get a location for subsequent evidence submission document upload PUT request
postEvidenceSubmissions body → 201400404422500
PUT
/sc-upload-path
Accepts Supplemental Claim Evidence Submission document upload
putScUploadPath 1 param → 200400500
GET
/evidence-submissions/{id}
Returns all of the data associated with a specific Supplemental Claim Evidence…
getEvidenceSubmissionsById 1 param → 200403404500

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are address_2 (8 properties), address (8 properties), phone (4 properties), contestableIssue (3 properties). Each schema is shown below with its type and property counts.

X-VA-Birth-Date
string
Veteran's birth date
scCreate
object
2 properties 2 required
contestableIssue
object
A contestable issue (to contest this, you include it as a RequestIssue when creating a HigherLevelReview, SupplementalClaim, or Appeal)
3 properties
X-Alternate-Signer-Last-Name
Alternate signer's last name
address
object
8 properties 4 required
X-VA-NonVeteranClaimant-First-Name
X-Alternate-Signer-First-Name
string
Alternate signer's first name
phone
object
4 properties 1 required
X-VA-Insurance-Policy-Number
timezone
string
X-VA-ICN
string
Veteran's Integration Control Number, a unique identifier established via the Master Person Index (MPI)
X-VA-NonVeteranClaimant-Last-Name
X-VA-NonVeteranClaimant-Middle-Initial
X-VA-File-Number
nonBlankString
string
errorModel
object
1 property 1 required
scCreateResponse
object
Successful response of a 200995 form submission
2 properties
X-VA-Last-Name
X-VA-SSN
string
social security number
X-VA-Middle-Initial
scEvidenceSubmissionResponse
object
1 property 1 required
X-VA-First-Name
X-Alternate-Signer-Middle-Initial
Alternate signer's middle initial
scEvidenceSubmissionCreate
object
JSON Schema for evidence submissions for VA Form 20-0995
2 properties 2 required
scCreate_2
object
JSON Schema for VA Form 20-0995
2 properties 2 required
ssn
string
Social Security Number
timezone_2
string
scEvidenceSubmissionResponse_2
object
1 property 1 required
icn
string
Veteran's Master Person Index (MPI) Integration Control Number (ICN)
appealableIssue
object
An appealable issue (to appeal this, you include it as a RequestIssue when creating a HigherLevelReview, SupplementalClaim, or Appeal)
3 properties
scCreateResponse_2
object
Successful response of a 200995 form submission
2 properties
address_2
object
8 properties 4 required
fileNumber
string
Veteran's VA file number (c-file / css)

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

va-supplemental-claims-api-openapi.yml Raw ↑
#Supplemental Claims
← Back to V APIs
API Details
ID
va:va-supplemental-claims-api
Base URL
https://api.va.gov/services/benefits-intake/v2
Docs
https://developer.va.gov/explore/api/benefits-intake
Provider
Va
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-supplemental-claims-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/va-supplemental-claims-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 Supplemental Claims 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.