Enterprise integration
ProofAudit.ai
Integration guide
Organized evidence for review and accountability. Use the customer portal to coordinate onboarding and manage credentials for your organization.
Your product endpoint
Use this address after your organization receives production access and integration approval. API calls require a product-specific credential and verified subscription access.
POST https://proofaudit.ai/api/v1/products/proofaudit/evaluate
Authorization: Bearer <your product API key>
Content-Type: application/jsonYour onboarding team configures the server policy for your contracted integration. Confirm activation and the required policy identifiers before sending production requests.
Assess and record an evidence manifest
Compare submitted artifact SHA-256 digests with the expected digests and case-bound approval records maintained by your onboarding team.
{
"caseId": "your-case-id",
"artifacts": [
{
"id": "your-artifact-id",
"sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
]
}Example identifiers and values only. Required fields must match your configured policy. Additional fields and caller-supplied policy or approval overrides are rejected.
Handle the result
ready, hold or block, with a manifestSha256 and lists of missing or mismatched items. A successful response also contains an evidenceId for the stored assessment. The manifest digest identifies the submitted digest list; it is not a signature or proof of the source documents’ authenticity. Responses include requestId, product, decision, reason, policyVersion and executionPerformed: false. Hold the proposed action on errors, timeouts or unknown outcomes.
Retrieve an evidence assessment
GET https://proofaudit.ai/api/v1/products/proofaudit/evidence/<evidenceId>
Authorization: Bearer <your ProofAudit API key>Only an active ProofAudit key belonging to the record’s organization can retrieve it. Stored records contain assessment metadata and the manifest digest, not raw documents. Repeated evaluations create separate records.
Credentials and request limits
Keep keys in your server-side secrets manager. Send them only in the Authorization header, never in a URL or browser code. Keys expire after 90 days and can be revoked through Customer access once credential management is activated.
The initial operational limit is 60 requests per minute per key with a maximum 16 KB request body. These are technical limits, not subscription allowances.
- 400
- Invalid request
- 401
- Missing or invalid API key
- 403
- Subscription access unavailable
- 413
- Request body too large
- 429
- Rate limit reached
- 503
- Service or integration unavailable
Do not retry rejected actions automatically. For 429 responses, use bounded backoff; for 503 responses, confirm service availability with support.