Developer portal
POST /pqc/verify
Public verification endpoint accepting proof payloads directly.
PilotPOST /pqc/verifyPublic
Summary
Public verification endpoint accepting proof payloads directly.
Example
curl
curl -X POST "https://sparkling-vibrancy-production-1a7a.up.railway.app/pqc/verify" \
-H "Authorization: Bearer 811f31d4-5b8e-4ed0-a7a2-8176e05eba63" \
-H "Content-Type: application/json" \
-d '{
"proof": {
"content_hash": "sha256:ab12...",
"signature": "base64..."
}
}'Request body
| Field | Type | Required | Description |
|---|---|---|---|
| proof | object | Yes | Signed proof payload generated from report artifacts. |
Errors
| Code | Meaning | Typical cause | Suggested fix |
|---|---|---|---|
| 404 | Not found | Scan, schedule, share link, or resource id does not exist or expired. | Verify id and tenant scope; share links expire per expiresHours. |
| 422 | Unprocessable entity | Invalid payload shape, unsupported scenario, or infeasible constraints. | Fix field errors in response detail; relax constraints and retry. |
| 429 | Too many requests | Per-key rate limit exceeded (default 300 requests per minute) or public endpoint limit. | Backoff with jitter; cache results; request higher limit for production. |
| 500 | Internal server error | Unexpected backend failure; includes requestId in response. | Retry with exponential backoff; contact support with requestId if persistent. |
See the full errors reference.
Found an issue? Report documentation feedback