Skip to main content
POST
Confirm / attach a company document
Step 2 of the company-document upload: confirm a document you already PUT to a presigned URL. It routes through the shared deposit core, so the document runs the same triage and kind-match gating and drives the same KYB completion recompute as an officer upload — ownership, size and file type are all re-checked server-side (the presigned URL only says where you may write). outcome: reading means it was accepted and queued for extraction; wrong-document means the initial check judged it not to be the expected document — replace it and confirm again. Requires the documents:write scope.

Authorizations

Authorization
string
header
required

Bearer API key issued from Settings → Developers in your Instant Compliance organisation. Format: ic_live_….

Path Parameters

id
string
required

Entity identifier (UUID or your external_id).

Body

application/json
s3Key
string
required
Required string length: 1 - 1024
file
object
required
note
string
Maximum string length: 2000

Response

The stored file / extraction-job ids and the triage outcome.

file_id
string<uuid>
job_id
string<uuid>
outcome
enum<string>

reading — accepted and queued for extraction. wrong-document — the initial check judged it not to be the expected document; replace it and confirm again.

Available options:
reading,
wrong-document