# ValidAPI.com — integration review checklist

Reference only. The website and its downloads do not provide a live validation API.

## Purpose and evidence
- Name the action the check supports.
- Identify the minimum input and context needed.
- Separate structure, normalization, consistency, source comparison, and holder linkage.
- Define what every pass, failure, unknown, and unperformed signal establishes.

## Actual provider and contract
- Confirm authorization, available methods, document types, and geographical coverage.
- Review the actual authentication, schema, version policy, limits, pricing, and availability terms.
- Do not treat the illustrative OpenAPI hostname or routes as operational.

## Recovery and state
- Map stable reason codes to correction, review, unsupported, and unavailable routes.
- Make every offered alternative a real supported process.
- Associate results with the exact input version; reject stale results.
- Bound automatic retries and reconcile duplicate work.

## Security and data lifecycle
- Keep production credentials out of public client code.
- Establish an approved collection channel before accepting documents.
- Map every destination: primary records, logs, queues, monitoring, support, vendors, and backups.
- Use diagnostic allowlists; avoid unnecessary record echoes.
- Define access, retention, deletion, and operational ownership based on the actual environment.

## Testing and launch
- Use fictional fixtures for public examples and ordinary contract tests.
- Test missing context, unsupported inputs, partial results, outages, delayed responses, and unknown codes.
- Review keyboard access, mobile layouts, and user-facing messages.
- Inspect diagnostics during failures for unnecessary personal information.
- Review all public claims against the deployed capabilities.

Contact: info@validapi.com. Do not send personal documents, credentials, or customer datasets.