Skip to main content
POST
/
api
/
v1
/
court-order
Create Court Order
curl --request POST \
  --url https://api.example.com/api/v1/court-order \
  --header 'Content-Type: application/json' \
  --data '
{
  "nullifier_hex": "<string>",
  "reason": "<string>",
  "pdf_url": "<string>"
}
'
{
  "order_id": "8b9cad0e-72a2-b281-0081-8b9cad0e1f20",
  "status": "pending",
  "message": "Court order created. 5 custodians must review — 3 approvals needed to proceed.",
  "expires_at": 1709428500.0
}
This endpoint is restricted to the Issuer. It alerts the 5 Key Custodians that a valid legal request has been made to deanonymize a specific nullifier_hex. To process this order, 3 out of the 5 Custodians must independently approve it via the Custodian Dashboard before the decryption key can be mathematically reconstructed.

​
Authentication

All issuer endpoints require the X-API-Key header.

​
Body

​
nullifier_hex
string
required
The 64-character hash of the target to be revoked or investigated.
​
reason
string
required
The legal justification, statute reference, or internal case number for the court order.
​
pdf_url
string
A secure link to the scanned, signed PDF order from the Judiciary. Custodians will review this document before voting.
{
  "order_id": "8b9cad0e-72a2-b281-0081-8b9cad0e1f20",
  "status": "pending",
  "message": "Court order created. 5 custodians must review — 3 approvals needed to proceed.",
  "expires_at": 1709428500.0
}