Skip to main content
POST
Upload Document
Part of the Onboarding Documents flow. The request is multipart/form-data with two fields: tag and file. Send one document per call; you may call it multiple times to upload the documents partially.

Path Parameters

uuid
string
required
UUID of the solicitation (the id returned by Create Company). Must be in a status that accepts uploads (pending_documents or documents_under_review).
  • Format: UUID
  • Example: 339074a8-1834-49c5-af94-4a044248d88d

Request Body

Content-Type: multipart/form-data.
tag
string
required
Identifier of the document being sent. Must match one of the tag values listed for the solicitation (delivered in the pending_documents webhook or returned by List Documents). An unrecognized tag is rejected with 422.
  • Example: articles_of_incorporation
file
file
required
The document file.
  • Accepted formats: pdf, jpg, jpeg, png
  • Maximum size: 10 MB

Behavior

  • A successful upload sets the document’s upload_status to sent.
  • After each upload, if all required documents are sent, the solicitation moves automatically to documents_under_review. Optional documents do not block this transition.
  • The onboarding webhook is fired on every upload, reflecting the updated state.
  • Resending a rejected document: uploading a document whose review_status is rejected sets upload_status back to sent and review_status back to pending. The previous rejection reason is preserved in the document history and is not returned in the active document state.
Upload is only allowed when the document’s upload_status is pending or its review_status is rejected. A document already approved cannot be replaced, and a document already sent and awaiting review cannot be re-sent — both return 422.

Response

message
string
Confirmation message.

Errors

Examples

Onboarding Documents Integration

Understand the full flow

List Documents

Query state and review history