Upload a file
POST/uploads
Stores the file and returns the upload created for it, which you can read right away at GET /uploads/{id}. Transfer then processes the file asynchronously.
Request
Responses
- 202
- 400
- 401
- 403
- 409
- 413
- 422
- 500
- 503
The upload receipt
Response Headers
URI of the created upload receipt.
The body is not valid JSON.
The token is missing, expired or invalid. Send Authorization: Bearer <token>.
The account is not enabled for the Transfer API or for this destination.
Nothing was stored. The type tells the case: /errors/transfer_not_configured when Transfer is not configured for this destination (a subaccount needs its own configuration, the one of its parent account does not apply), /errors/e2e_id_already_used when one of your target documents already has this e2e_id.
The body exceeds 5 MiB. The response body is not JSON.
A field is invalid: violations holds one entry per invalid field, with propertyPath set to the request field name (country, file_name, content, e2e_id).
The upload could not be created. Nothing was stored: you can send the file again.
The upload was created but its file could not be confirmed as stored (type /errors/upload_outcome_unavailable). Read the upload at Location, also in instance, before sending the file again: failed means nothing was stored.
Response Headers
URI of the created upload.