> ## Documentation Index
> Fetch the complete documentation index at: https://docs.generalvalidation.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API reference

> Use the General Validation SaaS API to discover metadata, manage tests, and run validations.

Send API requests to `https://api.generalvalidation.com` using the `/api/v1`
paths shown in this reference. Authenticate with a Microsoft Entra access token
for the General Validation API. Read [API authentication](/api-authentication)
before connecting a service or managed identity.

The pages in this reference cover request parameters, request bodies, required
roles, status codes, and response headers. For the complete response schemas,
retrieve `https://api.generalvalidation.com/openapi.json` with an authenticated
Reader token. Use `/openapi-agent.json` when your tool requires the compatible,
reduced schema described in the [Foundry guide](/connect-microsoft-foundry-agent).

## Choose a workflow

Use [API and automation](/api-and-automation) for the sequence from discovering
datasets to creating a Pair, defining tests, submitting a Run, and checking the
result. The endpoint groups in the sidebar provide the detailed request contract.

## Results and evidence

The hosted API returns safe result metadata and pointers. Exact source and target
values, deltas, and row evidence remain in customer storage. API access does not
grant storage access. See [Runs, results, and evidence](/runs-results-and-evidence).

Customer runtime delivery callbacks are configured by the execution-environment
setup. They are not general-purpose integration endpoints.