Workspace API Reference Documentation

Programmatically build, structure, evaluate, and synchronize your public endpoints utilizing the authoritative DocTight integration API layer.

The following technical documentation illustrates the workspace metadata layout models. This matches the exact deployment paradigm described within the system PRD specifications.

Core Document Endpoint Schema Model

Every programmatic node published to your live edge domain (e.g. docs.yourcompany.com) yields structured architectural objects following the core definition model below:

const docPayload = {
  id: "doc_7x9a2f1b4",
  workspaceId: "ws_noquestions_01",
  title: "Privacy Policy",
  slug: "privacy-policy",
  content: "# Privacy Policy\n\nYour authoritative text content here...",
  status: "published", // Draft or Published status options
  createdAt: "2026-06-17T10:47:27Z",
  updatedAt: "2026-06-17T10:47:45Z",
  version: 1
};

console.log("Initial active deployment payload synchronized successfully.");

curl -X POST https://api.doctight.com/v1/document/publish \
  -H "Authorization: Bearer dt_live_sec_key" \
  -H "Content-Type: application/json" \
  -d '{
    "workspaceId": "ws_noquestions_01",
    "title": "AI Usage Policy",
    "slug": "ai-usage-policy"
  }'

System Data Abstraction Layer Requirements

To align cleanly with modern enterprise security principles, the product's persistent architecture isolates production components within designated schema namespaces. Data mappings resolve efficiently down to the following underlying entity tables:

Workspaces Table: Holds global relational records linking brand identifiers down to physical web configurations (id, name, domain).

Documents Table: Tracks individual text assets containing structure states and live routing endpoints (id, workspaceId, title, slug, content, status).

Versions Table: Captures structural modifications seamlessly over time to enable rapid platform rollback capabilities (id, documentId, content, createdAt).

Discovery Engine Integration Specifications

Every workspace generated across our distribution edge dynamically crafts an index map designed specifically for consumption by autonomous search scrapers. It features native, immediate construction of access parameters including optimized semantic XML structures, detailed tracking patterns, and automated llms.txt content manifests.