Projected
HTTP APIs
Strategic roadmap; not shipped. No delivery date is committed.
Strategic roadmap: GET-only extraction from customer HTTP APIs with OpenAPI-assisted discovery, pagination and rate limits.
Integrations · APIs
API test data management
Many systems are only reachable through their HTTP APIs. Test data drawn from them has to respect the API contract, its paging and its rate limits.
An API read is still a read of production data, so it needs the same controls as a database query: read-only scopes, local processing and evidence.
What test data management needs here
- GET-only access with tokens scoped to read endpoints, supplied as secret references.
- OpenAPI-assisted discovery of resources and response shapes, where a description exists.
- Classification of response fields and masking before anything leaves the agent host.
How DataNivra approaches it
- API connectors are roadmap work; the design issues read-only methods by default and processes every response inside your network.
- Whatever the system, row-level work happens in the DataNivra agent inside your network: only metadata, aggregates and evidence reach DataNivra Cloud.
APIs: connector status (1)
None of these connectors can be used today. Each one below shows its honest status; the integration pages describe what you can do in the meantime. Statuses are derived from recorded conformance evidence.
Learn, try, then start
See the whole workflow — discovery, classification, masking, subsetting and certification — on synthetic data in the interactive demo, then start a free trial. The product overview explains how the customer-resident agent and DataNivra Cloud divide the work.
Other categories: Databases · Data warehouses · Lakehouses · Object storage · Files · NoSQL · SaaS applications · Mainframe · Streaming.