Controlled API access to the current workpaper contract.

Onboarding

Understand the V1 access model first.

1. Authenticate through the dashboardSign in at the product login. External API key access is not enabled in V1.
2. Retain the authenticated session cookieProtected GET and POST endpoints require the live session cookie from that sign-in.
3. Use CSRF token for calculate/export requestsSend X-CSRFToken with the session cookie on unsafe POST operations.
4. Access only records allowed by case membership and permissionsFinancial endpoints require can_view_financials. Calculation requires authenticated session access, case membership, financial-view permission, financial-edit permission, and a valid CSRF token.

curl -s https://exitprotocols.com/api/v1/capabilities/

curl -s -b cookies.txt \
  https://exitprotocols.com/api/v1/cases/

curl -s -X POST -b cookies.txt \
  -H "Content-Type: application/json" \
  -H "X-CSRFToken: <CSRF_TOKEN>" \
  -d '{"strategy":"neutral"}' \
  https://exitprotocols.com/api/v1/claims/<CLAIM_UUID>/calculate/

Reference

Endpoint directory

{
  "status": "ok",
  "service": "Exit Protocol API",
  "version": "v1"
}

{
  "libr_single_claim_workpaper": true,
  "multi_claim_pro_rata_default": false,
  "public_file_verification": true,
  "clio_selected_document_workflow": true,
  "legal_advice": false,
  "expert_report": false,
  "admissibility_guarantee": false
}

{
  "match_found": true,
  "calculated_hash": "abc123...",
  "record_type": "Generated Review Workpaper",
  "timestamp": "2026-06-19T12:00:00+00:00",
  "message": "Final file hash verified"
}

{"id": "…", "email": "counsel@firm.example", "is_authenticated": true}

{"cases": [{"id": "…", "case_number": "MAT-001", "role": "attorney_petitioner"}]}

{"account_id": "…", "transactions": [...], "pagination": {"page": 1, "page_size": 50, "total": 120}}

{"account_id": "…", "claims": [{"id": "…", "claim_name": "Premarital Savings", "last_strategy": "neutral"}]}

POST /api/v1/claims/<claim_id>/calculate/
{"claim_id": "…", "strategy": "neutral", "calculation_status": "complete", "current_traceable_amount": "8500.00", "lowest_intermediate_balance": "8200.00", "updated_at": "…"}

GET /api/v1/claims/<claim_id>/

{
  "calculation_status": "complete",
  "current_traceable_amount": "8500.00",
  "lowest_intermediate_balance": "8200.00",
  "last_strategy": "neutral",
  "updated_at": "2026-06-19T12:00:00+00:00"
}

{
  "status": "created",
  "report_id": "…",
  "file_hash_sha256": "…",
  "download_url": "https://exitprotocols.com/api/v1/reports/…/download/",
  "verification_url": "https://exitprotocols.com/verify/"
}

Integrity

What verification confirms — and what it does not.

• POST /api/v1/verify/ hashes uploaded bytes with SHA-256 before any match lookup.
• A match means uploaded bytes exactly match a recorded final-file hash in the integrity ledger.
• Renaming a file does not matter — matching is byte-exact, not filename-based.
• Editing or re-saving a PDF changes bytes and can fail matching even if content looks similar.
• Snapshot hash (integrity_hash) and final file hash are different artifacts; snapshot hash alone does not verify.
• Static synthetic sample PDFs may not be registered unless explicitly recorded in the ledger.
• Verification does not decide ownership, admissibility, or legal outcome — attorney or expert review is required.

Applications

API use cases

Live check

Try public endpoints

Select an endpoint to view the JSON response.