Integrations · APIs · Available now
HTTP APIs test data, inside your network
Generic HTTP/JSON API connector: you declare each resource in a schema contract (path, where the records are, id fields, field types or a JSON Schema, relationships, pagination) and the agent reads it with GET-only requests, rate limits and bounded reads inside your network.
Available now APIs
Shipped in the standard agent and backed by recorded conformance evidence.
What works today
Generic HTTP/JSON API connector: you declare each resource in a schema contract (path, where the records are, id fields, field types or a JSON Schema, relationships, pagination) and the agent reads it with GET-only requests, rate limits and bounded reads inside your network.
HTTPS with certificate verification by default; plain HTTP only with an explicit opt-in. Bearer token, basic, API-key header or OAuth 2.0 client credentials, all as secret references. Offset, page-number, cursor, next-link and Link-header pagination; 429 and Retry-After are honoured with bounded waits. Responses are processed inside your environment.
Authentication: bearer token (secret reference); basic (secret reference); API key header (secret reference); OAuth 2.0 client credentials (secret reference).
Known limitations
- Read-only access is attested by the operator, not verified by the connector.
- Keys and relationships come only from the schema contract. Resources without declared fields are sampled for field names and types, and only identifier-shaped names are accepted.
- JSON responses only. Nested objects and arrays are carried as JSON text; fields below the top level of a record are not flattened.
- Record counts page through the whole resource, bounded by max_pages and max_records.
- Verified against PostgREST (a REST API server over PostgreSQL). Other APIs depend on an accurate schema contract.
- Requires agent 0.4.0 or later; earlier agent images do not include this connector.
Capability matrix
Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.
| Capability | Level |
|---|---|
| Discovery | Supported |
| Classification | Supported |
| Profiling | Supported |
| Masking | Supported |
| Deterministic masking | Supported |
| Entity-aware subsetting | Supported |
| Relationship preservation | Supported |
| Synthetic workflows | Supported |
| Certification | Supported |
| Provisioning | Supported |
| CI/CD | Supported |
| Evidence generation | Supported |
Read-only proof
A generic API has no permission model the agent can inspect, so you attest that the credential is read-only; without that attestation the source is refused. Independently, the connector's transport lets only GET and HEAD requests reach the API and refuses redirects and next-page links that leave the configured origin.
Conformance evidence
DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.
| Engine or service | Version | Environment | Driver | Authentication | Verified on |
|---|---|---|---|---|---|
| PostgREST | 13.0.4 | real-engine | httpx 0.28.1 | bearer JWT (read-only attested) | 2026-10-08 |
Connector version 0.1.0, last verified 2026-10-08.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Setup outline
- Use agent 0.4.0 or later (earlier agent images do not include the HTTP API connector).
- Issue a credential the API itself limits to reading the resources you need (a read-only token, scope or role). The connector cannot check this, so you attest it with "read_only_attested": true; without the attestation the source is refused.
- Describe each resource in the connection document: its path under base_url, where the records are (records_pointer), its id_fields, field types (or a JSON Schema), relationships to other resources and how it pages.
- Store the document with the token, password, API key or OAuth client secret as a secret reference. HTTPS with certificate verification is the default; plain HTTP needs "allow_plain_http": true.
- In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
- The agent sends GET and HEAD requests only, never follows a redirect or next-page link to another origin, and processes every response inside your network.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "HTTP_API",
"base_url": "https://claims-api.example.internal/v2",
"auth": "bearer",
"token_ref": "vault://tdm/claims-api#read_token",
"read_only_attested": true,
"resources": {
"members": {
"path": "/members",
"records_pointer": "/data",
"id_fields": ["member_id"],
"fields": { "member_id": "string", "last_name": "string", "birth_date": "date" },
"pagination": { "type": "cursor", "next_pointer": "/next_cursor", "cursor_param": "cursor" }
},
"claims": {
"path": "/claims",
"records_pointer": "/data",
"id_fields": ["claim_id"],
"fields": { "claim_id": "string", "member_id": "string", "billed": "decimal(12,2)" },
"relationships": [
{ "fields": ["member_id"], "resource": "members", "resource_fields": ["member_id"] }
],
"pagination": { "type": "offset", "size_param": "limit", "page_size": 500 }
}
}
}Next: install the agent, then follow the getting started guide.
All integrations · API test data management · Guides · Start free