Overview
After all files have been uploaded to a job, call this endpoint to close the upload window and trigger Plangrep processing. The job transitions throughpreflighting and then into processing.
This endpoint is safe to call multiple times with the same Idempotency-Key — duplicate calls within the idempotency window return the original response without re-triggering processing.
Endpoint
Authentication
All requests must include a Bearer token in theAuthorization header.
Path Parameters
The unique identifier of the job whose uploads you are completing.
Request Headers
An optional client-generated idempotency key (max 256 characters). If a request with this key has already succeeded, the server returns the original response and sets
idempotent: true in the body. Use a UUID or other unique value per completion attempt.Request Body
Content-Type:application/json (optional)
The request body is optional. For jobs where files were uploaded via POST /api/open/v1/jobs/{jobId}/files, send an empty object {} or omit the body entirely.
For jobs using registered uploads, the body carries completion payloads for each upload mode.
An explicit list of document IDs to include in this completion. When omitted, all documents uploaded to the job are included.
Completion records for files uploaded via the
direct_put flow (registered uploads). Each entry must include:The document ID returned during registration.
The upload token returned during registration. Proves the direct PUT was performed.
Completion records for files uploaded via the
multipart flow (registered uploads). Each entry must include:The document ID returned during registration.
The multipart upload ID returned during registration.
The upload token returned during registration.
Records of uploads that failed on the client side. Reporting these allows Plangrep to mark the corresponding documents and surface errors in the job result rather than waiting for a timeout.
Response
Status:202 Accepted
The updated Job object. Immediately after this call the job status will begin transitioning to
preflighting, then processing.Present and
true when the response was served from a previously completed idempotent request. Absent on first-time completions.Job Status Transitions
202, poll the job status or use webhooks to detect when processing finishes.