API archive entry · source-reported
VA Facilities
## Background This RESTful API provides information about physical VA facilities. Information available includes geographic location, address, phone, hours of operation, and available services. VA operates several different types of facilities, the types represented in this API include: - Health Facilities (vha) - Benefits Facilities (vba) - Cemeteries (nca) - Vet Centers (vc) To read an FAQ on how wait times are calculated, click the "For more information" link on this page. ## Getting Started ### Base URLs The base URLs for the VA Facilities API in the various environments are: - Sandbox: `https://sandbox-api.va.gov/services/va_facilities/v0` - Production: `https://api.va.gov/services/va_facilities/v0` ### Authorization API requests are authorized through a symmetric API token, provided in an HTTP header with name `apikey`. ### Response Formats Clients may request several response formats by setting the `Accept` header. - `application/json` - The default JSON response format complies with JSON API. This media type is *not* available for bulk requests using the `/facilities/all` endpoint. It will return `406 Not Acceptable`. - `application/geo+json` - GeoJSON-compliant format, rep
Plan the first integration safely
The access fields below come from the connected directory. Their likely implementation impact is explained without assuming provider-specific behavior.
Authentication
OAuth is reported. Confirm flows, scopes, consent, token lifetime, and refresh rules.
Transport
HTTPS is not confirmed. Do not send credentials or production data until secure transport is verified.
Browser access
CORS is unknown. Treat direct browser access as unconfirmed and test before choosing a client-only architecture.
First-request sequence
- Identify the current base URL, version, and endpoint for the use case.
- Confirm how credentials are issued and where they may be stored.
- Test success, invalid input, throttling, unavailable data, and timeouts.
- Record response fields, pagination, caching, and error shapes.
- Add monitoring, retries with backoff, and an appropriate fallback.
Questions to resolve before production
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Source reference
This page separates source-reported facts from questions that need live provider verification.