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 Lighthouse

VA Lighthouse Intent to File API

Used for 0966 submissions.

Documentation Provider Profile APIs.io OpenAPI GitHub

VA Lighthouse Intent to File API is one of 35 APIs that VA Lighthouse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Intent To File. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a changelog, and authentication docs.

This API exposes 7 operations across 6 paths. It is described by OpenAPI 3.0.1, at version 3.

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

7 operations 6 paths 0 schemas 3 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3
Base URL
https://api.va.gov/services/va_facilities/v1
Authentication
API Key
License
Creative Commons
Resource Areas
1

Authentication & Security 1

VA Lighthouse Intent to File API declares 1 security scheme for authenticating requests. An API key is passed in the header as apikey (apikey). By default, every request must be authenticated.

Paths & Operations 7

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

Intent to File 7

Used for 0966 submissions.

GET
/forms/0966deprecated
Get 0966 JSON Schema for form.
GET:/forms/0966 → 200413429504
POST
/forms/0966
Submit form 0966 Intent to File.
POST:/forms/0966 4 params body → 200401403413422429504
GET
/forms/0966/active
Returns last active 0966 Intent to File form submission.
GET:/forms/0966/active 5 params → 200401404413422429504
POST
/forms/0966/validatedeprecated
Test the 0966 Intent to File form submission.
POST:/forms/0966/validate 4 params body → 200401413422429504
GET
/veterans/{veteranId}/intent-to-file/{type}
Returns claimant's last active Intent to File submission for given benefit type.
GET:/veterans/{veteranId}/intent-to-file/{type} 2 params → 200401404413429504
POST
/veterans/{veteranId}/intent-to-file
Submit form 0966 Intent to File.
POST:/veterans/{veteranId}/intent-to-file 1 param body → 200400401404413422429502
POST
/veterans/{veteranId}/intent-to-file/validate
Validate form 0966 Intent to File.
POST:/veterans/{veteranId}/intent-to-file/validate 1 param body → 200400401413429504

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

va-gov-intent-to-file-api-openapi.yml Raw ↑

Other APIs VA Lighthouse publishes across the network.

Decision Reviews API
AE Profile APIs.io
Education Benefits API
AE Profile APIs.io
Loan Guaranty API
AE Profile APIs.io
Guaranty Remittance API
AE Profile APIs.io
Health Care Costs Coverage API
AE Profile APIs.io
VA Lighthouse 5103 Waiver API
AE Profile APIs.io
VA Lighthouse ACA Coverage API
AE Profile APIs.io
VA Lighthouse AddressValidation-v3 API
AE Profile APIs.io
VA Lighthouse Appealable Issues API
AE Profile APIs.io
VA Lighthouse Appeals Status API
AE Profile APIs.io
VA Lighthouse Claims API
AE Profile APIs.io
VA Lighthouse DirectDeposit API
AE Profile APIs.io
#Intent To File
← Back to V APIs
API Details
ID
va-gov:va-gov-intent-to-file-api
Base URL
https://api.va.gov/services/va_facilities/v1
Docs
https://developer.va.gov/explore/api/va-facilities/docs
Provider
VA Lighthouse
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-gov-intent-to-file-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/va-gov-intent-to-file-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 VA Lighthouse Intent to File 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.