Test Data API
Profiles, plans, requests, waiting and release — the programmable entry point to approved test data.
Build on DataNivra Test Data Management (TDM)
The same customer-resident TDM engine your data team runs from the console, reachable from code, pipelines and AI agents under policies your administrators approve.
Start here
Runnable examples
Synthetic scenarios by sector, language, QA framework and CI provider, with expected output.
REST API reference
Every v1 operation, generated from the route contract.
CLI
The datanivra command line: login, test-data, env-leases, certificates and more.
What is available today
| Capability | Status | Details |
|---|---|---|
| TDM console, agent, connectors and industry packs | Available | The existing TDM product: discovery, subsetting, masking, synthesis, certification and provisioning. |
| Test-data profiles, plan, request, wait and release (REST, CLI) | In repository | Implemented and tested in the repository; not yet deployed to the hosted service. |
| YAML/JSON manifests (TestDataProfile, TestDataRequest) | In repository | Safe parser, strict validation and canonical checksums in the CLI and both SDKs. |
| Python and TypeScript SDK helpers | Not published | Not yet published to PyPI or npm; install from the repository or release assets. |
| CI workload identity (GitHub Actions, GitLab CI OIDC) | Off by default | Implemented and tested; a deployment must enable it before any pipeline can sign in. |
| Automatic approval inside a human-approved envelope | Off by default | Preview: needs the operator switch and the tenant switch; otherwise a person approves. |
| MCP adapter for AI agents | Local only | Preview: a local stdio adapter that calls the same API with your own session; no hosted MCP endpoint. |
Documentation
Test Data API overview · Profiles and manifests · CI workload identity · Automatic approval · CI recipes · MCP adapter · Troubleshooting