Prefiler operates as a stable, headless RESTful API. Integrating systems securely request upload URLs, enqueue asynchronous analyses, and fetch reproducible verification reports via standard HTTP endpoints.
Factual Note: The payloads, rule IDs, and version numbers displayed below are representative, synthetic examples for B2B integration modeling. They do not constitute actual deployed facts.
Integrators request a secure, tenant-scoped upload URL to transmit source files directly to the storage layer.
{
"content_type": "application/pdf"
}// Response (200 OK){
"input_id": "inp_demo_001",
"upload_url": "https://storage.googleapis.com/..."
}Submit an analysis request idempotently. The API responds instantly, processing large datasets asynchronously via Cloud Tasks.
Idempotency-Key: req_abc123
{
"input_id": "inp_demo_001"
}// Response (202 Accepted){
"id": "an_demo_001",
"status": "queued"
}Retrieve the completed evaluation via stable DTOs. Findings index arithmetic variances, missing evidence, and required reviews.
// Response (200 OK)
{
"id": "an_demo_001",
"status": "completed",
"findings": [
{
"finding_id": "finding_demo_001",
"category": "gross_receipts_variance",
"severity": "high",
"variance": 194500,
"requires_professional_review": true
}
]
}Requests are authenticated via static secure Bearer tokens mapped per API Tenant, passed in request headers.
Prevent duplicate transactions by passing required client-generated Idempotency-Key headers on start calls.
For large files, Prefiler provides an asynchronous job status pattern. Poll the status endpoint at /v1/analyses/{id}.
Calculations are rule-based, deterministic, and pinned to selected filing years, guaranteeing reproducible audits.
The external JSON outcome is completely decoupled from our internal database schemas and intelligence models.
If a required statement or form is absent, Prefiler returns a structured error payload detailing the missing inputs.
Structured /clarifications endpoints allow fetching questions and posting answers for human-in-the-loop workflows.
Prefiler operates strictly in-memory. Volatile raw file buffers are immediately flushed from RAM post-processing.
Contact our technical team to schedule a walkthrough, request API schema specifications, or review private dedicated deployment options.