Version: 1.0.0
ZTeraDB Rest document
Welcome to the ZTeraDB REST API Specification. This document serves as the centralized technical guide for interacting with ZTeraDB's data-layer infrastructure.
The architecture is systematically divided into two decoupled layer clusters:
- Authentication Framework (
/auth): A cryptographically isolated, zero-exposure handshake service designed to issue short-lived operational tokens via complex local validation. - Schema Query Management Engine (
/schema-query): High-throughput transactional data nodes allowing structured CRUD capabilities over distributed cluster schemas using ULID resource tracking keys.
📂 Core Infrastructure Functional Domains
- The Identity Pipeline (
/auth/login): Mitigates man-in-the-middle (MITM) and classic packet replay exploits. By computing zero-knowledge local verification loops inside custom request tracking variables, core secrets never cross public network boundaries. - The Structural Data Engine (
/schema-query/.../{schema_name}): Handles direct table queries, structural mutations, data creation, and logical lifecycle purging. Execution paths are tied to unique enterprise instance identifiers to isolate operations safely across multi-tenant profiles.
Authentication
- API Key: ClientKeyAuth
- API Key: NonceAuth
- API Key: TimestampAuth
- API Key: RequestTokenAuth
- API Key: AccessTokenAuth
- API Key: EnvAuth
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Client-Key |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Nonce |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Timestamp |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Signature |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Access-Token |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Env |