Upload a file for a submission, a post or a quiz answer
The upload session API, as the calling person. With content_base64 the file is stored and scanned at once and its file_id returned. Without it a session is opened: PUT the bytes to put.url, then complete the session; the address goes straight to object storage where the deployment uses it.
Quire permissions
Credential scopes: me:write.
The acting subject must also be allowed to perform this action in the organisation.
https://your-organisation.quirelms.com/api/v1/me/uploadsAuthorisation
Header parameters
Request bodyJSONrequired
Returns
201
Success.
401
The credential is missing, malformed, expired or revoked.
403
The credential lacks the scope this operation requires, or the acting subject lacks the capability.
409
The request conflicts with the current state, with a previous use of the same idempotency key, or with a concurrent write.
422
The request was understood and its content is not valid. errors names each field.
429
A rate limit or a concurrency cap was reached. Retry-After says when to try again.
500
Something failed at our end. Quote request_id when reporting it.