VA Forms
VA Forms
Search VA forms, retrieve a form by name, and pull the PDF link or version metadata programmatically.
Keeps the surface simple with /forms and /forms/{form_name}
The scope is limited to the forms catalog, not the application process itself
Start with an API key and call /forms to validate search behavior. Then fetch /forms/{form_name} for a known form and confirm the PDF link, metadata, and version fields match your use case.
Uptime · 30-day window
About this API
This API is intentionally narrow: it exposes the VA forms catalog and per-form detail so that portals or internal tools can point to official PDFs and version metadata directly. Concrete nouns in the spec include "/forms" and "/forms/{form_name}".
That is enough to support search the va forms catalog, fetch metadata for a specific form name, and check whether a form has a newer version. The OpenAPI document names security schemes such as "apikey".
The scope is limited to the forms catalog, not the application process itself The API uses an API key requirement
What you can build
- 1Search the VA forms catalog
- 2Fetch metadata for a specific form name
- 3Check whether a form has a newer version
Strengths & limitations
Strengths
- Keeps the surface simple with /forms and /forms/{form_name}
- Explicitly includes PDF link and metadata use cases
- Fits search or synchronization jobs well
Limitations
- The scope is limited to the forms catalog, not the application process itself
- The API uses an API key requirement
Example request
curl https://va.gov/<endpoint> \
-H "Authorization: Bearer $API_KEY"
# Some providers use X-Api-Key instead — verify in the docs.Getting started
Start with an API key and call /forms to validate search behavior. Then fetch /forms/{form_name} for a known form and confirm the PDF link, metadata, and version fields match your use case.
Technical details
- Auth type
- api_key
- Pricing
- unknown
- Protocols
- REST
- Response time
- 738 ms
- Last health check
- 5/12/2026, 7:38:34 AM