Apply for access to the Veteran Service History and Eligibility API at developer.va.gov; select the OAuth 2.0 Authorization Code Grant flow for veteran-facing applications, or the Client Credentials Grant (CCG) for backend system-to-system access.
For CCG, exchange your RSA private key assertion for a bearer token at the VA token endpoint (https://api.va.gov/oauth2/token) using the client_credentials grant type and the required scope (e.g., veteran_verification.read).
Call GET /services/veteran_verification/v2/status to confirm whether the authenticated user is a confirmed Veteran; the response contains a veteran_status field (confirmed or not confirmed).
Call GET /services/veteran_verification/v2/service_history to retrieve a list of service episodes; each episode includes branch_of_service, begin_date, end_date, discharge_status, and service_type fields.
Call GET /services/veteran_verification/v2/disability_rating to retrieve the veteran's combined disability rating percent and a list of individual ratings if the scope permits.
In sandbox, use VA-provided synthetic veteran test credentials; do not use real veteran PII in the sandbox environment.
Known gotchas
The veteran_status confirmation is based on DoD data surfaced through VA — some recent separatees may not yet appear as confirmed until data propagates; advise veterans to allow several weeks after separation.
CCG (system-to-system) access requires scheduling a production access demo with the VA Lighthouse team and completing a security review; sandbox approval does not automatically grant production access.
Disability rating data is sensitive PII under the Privacy Act; ensure your application's data handling practices are consistent with the VA's terms of service and applicable federal privacy regulations.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp