ZeqTrial — Clinical Data Integrity
Clinical trial data integrity with ZeqProof-chained observations. Every data point carries a cryptographic proof binding it to the exact Zeqond it was recorded — tamper-evident by design.
| Endpoint | POST /api/health/trial/record |
| Auth | api-key |
| Rate limit | 60/min |
| Category | healthcare |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
trialId | string | Yes | Clinical trial identifier. |
observation | object | Yes | Observation data payload. |
subjectId | string | Yes | Subject identifier (hashed). |
Returns
{ recordId, zeqProof, zeqond, chainPosition, previousProof, integrity }
Example
curl -sS -X POST \
-H "Authorization: Bearer zsm_..." \
-H "Content-Type: application/json" \
-d '{
"trialId": "<trialId>",
"observation": {},
"subjectId": "<subjectId>"
}' \
"https://zeqsdk.com/api/health/trial/record"
This protocol is a named building block — one of the operations you
compose inside a state contract. Call it directly with
the request above, or invoke it from a contract that fires on your machine's
clock. Browse the whole library at GET /api/protocols; fetch this one at
GET /api/protocols/zeq-trial.