Skip to main content
POST
Advance saved processing
Advance retained processing only when the saved case supplies a continuation. The endpoint below uses the canonical Ultiwrite OpenAPI contract. This operation uses POST, preserves the original case and evidence, and does not consume another analysis credit. Its admitted HTTP request still counts toward the account’s request allowance. Use bounded retries and an overall workflow deadline. A timeout does not prove processing stopped; retain the case ID and resume the same case. Follow the workflow and error recovery guide.

Authorizations

Authorization
string
header
required

Create a key at /settings/api after an administrator approves your account. The key is shown once, can be revoked, and shares the account request allowance with other keys and partner OAuth grants. Send only in Authorization. These keys are not accepted by MCP or the legacy provisioned routes.

Path Parameters

caseId
string
required

Case id returned by this API.

Required string length: 1 - 80
Pattern: ^[A-Za-z0-9_-]+$

Response

Current workflow state after advancing.

state
enum<string>
required

persisted: this request created the case. already_persisted: the same package or case already existed.

Available options:
persisted,
already_persisted
caseId
string
required
Required string length: 1 - 80
Pattern: ^[A-Za-z0-9_-]+$
status
enum<string>
required

complete only when a report was saved. Not a conclusion.

Available options:
processing,
action_required,
complete,
failed
reportId
string | null
required
reportStatus
string | null
required
analysisRunId
string | null
required
documentForensics
boolean | null
required

The frozen document-forensics choice for this case.

artifactCount
integer
required
recordCount
integer
required
comprehensiveExecution
boolean
required
coverage
object
required
usage
object | null
required

Allowance after this request, when the account is metered.

nextAction
string
required
conclusion
null
required
meaning
string
required
processing
object