Skip to main content
POST
Finalize documentation file upload

Authorizations

Authorization
string
header
required

Use your API key as a Bearer token. API keys can be generated in Settings → Integrations → API Access.

Path Parameters

id
string<uuid>
required

documentId from the prepare call

Body

application/json

Send the same body to prepare and finalize; finalize checks the stored bytes against it.

name
string
required

Title shown in the documentation library, e.g. 'Invoice 2026-1042'

Required string length: 1 - 255
Example:

"Invoice 2026-1042"

fileName
string
required

File name with its extension: .pdf, .docx, .xlsx, .xls or .csv

Required string length: 1 - 255
Example:

"invoice-2026-1042.pdf"

fileSize
integer
required

Exact size in bytes, at most 50 MiB

Required range: 0 < x <= 52428800
Example:

48213

contentType
string
required

MIME type of the file. The response's contentType is the one to send on the PUT.

Required string length: 1 - 200
Example:

"application/pdf"

companyId
string<uuid>

Company (client) the document belongs to; its portal users can open it. Required unless folderId is a folder pinned to a company: a file without a company would be visible to every client, so it is refused.

folderId
string<uuid>

Custom folder ID (the UUID of a custom: key from the folders endpoint), e.g. an 'Invoices' folder. A folder pinned to a company only accepts that company.

Response

File document created

data
object
required