ProofSyncer

Document operations API

Connect ProofSyncer to the systems you already run.

The direct ProofSyncer service and public Apify Actor remain independent. Enterprise API keys have limited permissions, expire, can be revoked, and support safe per-document retries inside batches.

View pricing
Example result
{
  "batchStatus": "processing",
  "completed": 42,
  "needsAttention": 3,
  "delivery": "signed"
}

What you get

Ready work with a clear decision trail.

Single-document and batch ingestion
Limited and expiring API credentials
Safe duplicate-request and batch-item protection
Signed result deliveries with retries

How it works

  1. 1Create a limited API key
  2. 2Create a batch or send one document
  3. 3Upload each batch item with a stable item key
  4. 4Close the batch and monitor or export results

Integration reference

A focused API with enterprise safeguards.

Create an expiring key from Connections. Send it as a Bearer token. Keys can be limited to read or write access, revoked immediately, and are rate-limited per minute. Files remain limited to 8 MB and PDFs to 10 pages; API batches accept up to 500 independently uploaded items and 200 MB in aggregate.

POST
/api/v1/documents

Add one PDF, PNG, JPEG or WebP file. Use an Idempotency-Key to make retries safe.

POST
/api/v1/documents/{id}/process

Start the protected extraction and validation workflow immediately.

GET
/api/v1/documents/{id}

Read safe job, result, evidence, rule and route information.

POST
/api/v1/batches

Create a durable import batch for up to 500 expected items.

POST
/api/v1/batches/{id}/documents

Upload one bounded file with a stable itemKey and sequence. Never send a giant file array.

POST
/api/v1/batches/{id}/close

Close uploads and release accepted items to background processing.

GET
/api/v1/batches/{id}

Read batch counts and per-document progress.

GET
/api/v1/batches/{id}/export?format=csv

Download safe structured results and item errors as CSV or JSON.

Safe retries

Reuse the same 8–120 character Idempotency-Key for a single document. Inside a batch, keep the same 8–64 character itemKey when retrying one file.

Signed outcomes

Deliveries include a unique event ID, Unix timestamp and HMAC-SHA256 signature. Receivers should verify the signature and deduplicate the event ID.