cicora.ai
English
API specificationAttachments

Files and attachments

Upload a file through a dedicated operation, retain its id, and pass a reference in a later compatible request.

Integration reference: choose parameters and available capabilities from your account API settings and the model catalogue for your environment.

Upload the source

Check file type, size, rights, and retention before sending. A file should receive a stable id instead of relying on a name that a user can change.

Send binary content through multipart where the route requires it. Do not encode a large file into JSON when an operation expects multipart.

Upload a file for a later request
bash
curl --request POST https://cicora.ai/api/v1/files \
  --header "Authorization: Bearer $CICORA_API_KEY" \
  --form 'file=@analysis.pdf'

Attach to a request

  • Associate a file id with owner, project, and retention date.
  • Use only an attachment type supported by the model.
  • Keep a source file separate from extracted text and derived artifacts.

Delete and audit

Delete temporary attachments according to your retention schedule and owner requests.

Keep file id and metadata in a journal rather than copying its content when content is not needed for support.

Continue with