Quick Start — Extract, Seal, Verify

Generate an API key from the console. Keys follow the format dda_live_* and are scoped to specific operations.

Call POST /v1/extract to interpret natural-language content into a structured affective record. The response contains an EDM artifact — Essential (31 fields), Extended (62), or Full (91 fields).

curl -X POST https://deepadata.com/api/v1/extract \
  -H "Authorization: Bearer dda_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "I felt a deep sense of relief today after finally resolving the conflict with my colleague.",
    "jurisdiction": "GDPR",
    "consent_basis": "consent"
  }'

{
  "success": true,
  "data": {
    "artifact": {
      "meta": { "id": "edm_abc123...", "version": "0.8.3" },
      "core": {
        "anchor": "Finally resolving a workplace conflict",
        "spark": "Relief after conflict resolution"
      },
      "constellation": {
        "emotion_primary": "relief",
        "emotion_subtone": ["contentment"]
      },
      "governance": {
        "jurisdiction": "GDPR",
        "consent_basis": "consent"
      }
    }
  }
}

Save the artifactobject — you'll use it in the next step.

Call POST /v1/issue to seal the artifact into a .ddna envelope with a W3C Data Integrity Proof. This creates an immutable, verifiable record with a certificate of issuance.

curl -X POST https://deepadata.com/api/v1/issue \
  -H "Authorization: Bearer dda_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "artifact": { ... },
    "pathway": "delegated",
    "authority": "app:your-platform"
  }'

{
  "success": true,
  "data": {
    "envelope": {
      "ddna_header": { "version": "1.0", "format": "ddna" },
      "edm_payload": { ... },
      "proof": {
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "did:key:z6Mk...",
        "proofValue": "z5vgFc8h2YR3..."
      }
    },
    "certificate_id": "cert_8f7a3b2c...",
    "conformance_level": "sealed"
  }
}

Save the envelope and certificate_id for verification and audit trails.

Call GET /v1/verify/{certificate_id} with the certificate_id from Step 3. This is a public endpoint — no API key required. Anyone can verify a sealed artifact independently.

curl https://deepadata.com/api/v1/verify/CERTIFICATE_ID

{
  "success": true,
  "data": {
    "certificate_id": "cert_8f7a3b2c...",
    "issuer_did": "did:key:z6Mk...",
    "conformance_level": "sealed",
    "status": "valid",
    "certification_checks": {
      "schema_valid": true,
      "provenance_intact": true,
      "consent_attested": true,
      "governance_complete": true,
      "non_biometric": true
    },
    "issued_at": "2026-03-18T10:30:01Z"
  }
}

For applications with ongoing conversations — companion AI, journaling, therapy platforms — use POST /v1/ingest instead of /v1/extract. DeepaData automatically detects semantic boundaries and triggers extraction when a meaningful moment has accumulated.

curl -X POST https://deepadata.com/api/v1/ingest \
  -H "Authorization: Bearer dda_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "User turn text here",
    "role": "user",
    "subject_id": "vp-01...",
    "session_id": "session-abc",
    "sensitivity": "balanced"
  }'

DeepaData buffers conversation turns and triggers extraction automatically at semantic boundaries. When a moment is extracted, it is sealed as a governed .ddna artifact and added to the subject's registry.

To retrieve all artifacts for a subject, use GET /v1/subjects/{vp_id}.