Skip to content
GET/api/v1/privacy/assessments

List DPIAs

Lists the org's privacy / AI impact assessments — all five types (`dpia`, `tia`, `lia`, `ai_ia`, `pia`), not DPIAs alone. `?orgId` is required (400 MISSING_ORG_ID). Returns up to 500 rows ordered by `updated_at` descending, each a summary row: `{id, org_id, project_id, activity_id, assessment_type, title, status, ai_risk_class, overall_risk, approved_at, next_review_at, created_at, updated_at}`. The risk register, mitigations and reviewer detail are not part of this projection. GDPR Art. 35 requires a DPIA for high-risk processing; `assessment_type='dpia'` rows are the ones that satisfy it.

Authentication

Send Authorization: Bearer YOUR_API_KEY on every request. Generate API keys at /dashboard/settings/api-keys.

Response

200 example

{
  "success": true,
  "data": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "org_id": "00000000-0000-0000-0000-000000000000",
      "project_id": "00000000-0000-0000-0000-000000000000",
      "activity_id": "00000000-0000-0000-0000-000000000000",
      "assessment_type": "dpia",
      "title": "string",
      "status": "draft",
      "ai_risk_class": "minimal",
      "overall_risk": "low",
      "answers": {},
      "reviewer_id": "00000000-0000-0000-0000-000000000000",
      "approved_at": "2026-01-01T00:00:00.000Z",
      "next_review_at": "2026-01-01T00:00:00.000Z",
      "created_at": "2026-01-01T00:00:00.000Z",
      "updated_at": "2026-01-01T00:00:00.000Z"
    }
  ]
}

All status codes

200DPIAs.
400(no description)
401(no description)
403Forbidden — the credential is valid but lacks the API-key scope, member role, or plan entitlement this operation requires.
429(no description)
500Internal Server Error — DB_ERROR.

Code samples

cURL

curl -X GET \
  https://evalguard.ai/api/v1/privacy/assessments \
  -H "Authorization: Bearer $EVALGUARD_API_KEY"

TypeScript

// The TypeScript SDK (@evalguard/sdk) exposes TYPED methods — runEval,
// getEval, runSecurityScan, checkFirewall, … — not a generic request().
// For an arbitrary endpoint, call it directly:

const res = await fetch("https://evalguard.ai/api/v1/privacy/assessments", {
  method: "GET",
  headers: { Authorization: `Bearer ${process.env.EVALGUARD_API_KEY}` },
});
console.log(res.status, await res.json());

Python

# The Python SDK (pip install evalguardai) exposes TYPED methods on
# EvalGuardClient — run_eval, get_eval, … — not a generic request().
# For an arbitrary endpoint, call it directly:

import os
import requests

headers = {"Authorization": f"Bearer {os.environ['EVALGUARD_API_KEY']}"}

response = requests.request("GET", "https://evalguard.ai/api/v1/privacy/assessments", headers=headers)
print(response.status_code, response.json())

Go

package main

import (
	"context"
	"fmt"
	"net/http"
	"os"
)

func main() {
	req, _ := http.NewRequestWithContext(context.Background(), "GET", "https://evalguard.ai/api/v1/privacy/assessments", nil)
	req.Header.Set("Authorization", "Bearer "+os.Getenv("EVALGUARD_API_KEY"))
	resp, err := http.DefaultClient.Do(req)
	if err != nil { panic(err) }
	defer resp.Body.Close()
	fmt.Println(resp.Status)
}

Errors

400401403429500

Other Compliance endpoints