Upload a file with multipart/form-data and receive a reusable fileId. Stores bytes only; does not link the file to any other resource. Use the returned fileId with a separate attach call to put the file to work.
multipart/form-data and receive a reusable fileId. This endpoint stores bytes only — it does not link the file to a person, a business entity, or a participant document. Use the returned fileId with a separate attach call to put the file to work.
This is the only Commenda Partner API endpoint that accepts binary content. Files are scoped to the customer named in the path and can be referenced by any downstream attach call that takes a fileId for that customer.
fileId. A single fileId can be reused across multiple attach calls without re-uploading bytes.
file containing the binary body. The part’s filename and detected MIME type are stored as fileName and mimeType on the file record. No other fields are accepted.
| Limit | Value |
|---|---|
| Maximum file size | 100 MB per request |
| Request timeout | 120 seconds |
| Accepted MIME types | application/pdf, image/png, image/jpeg, image/heic, image/heif, image/tiff, image/webp, application/msword, application/vnd.openxmlformats-officedocument.wordprocessingml.document |
413 Payload Too Large. Requests with an unsupported MIME type return 415 Unsupported Media Type. Commenda detects the MIME type from the uploaded part’s content rather than trusting the declared Content-Type alone, so renaming a file extension does not change which limits apply.
If you need to upload files larger than 100 MB, contact Commenda. A separate direct-to-object-storage upload flow is available for those cases.
Commenda customer identifier.
Binary file part. The part filename and detected MIME type are recorded on the file. No other multipart fields are accepted.
File uploaded successfully