Files

The files endpoint stores a file once so you can reference it by id in any number of chat requests instead of re-encoding the bytes into every message. It follows the OpenAI files schema, so an OpenAI-compatible Go client pointed at https://opendunes.com/api/v1 can drive it through its files service — check your installed SDK version's own documentation for the exact call shape. Uploads and storage are free.

Upload a file#

The endpoint itself is a standard multipart POST — this is the full wire surface any Go HTTP client can target directly:

curl https://opendunes.com/api/v1/files \
  -H "Authorization: Bearer $OPENDUNES_API_KEY" \
  -F "file=@report.pdf"

A successful upload returns 201 with the file object — keep the id and reference it in chat requests.

Reference it in a chat request#

Send a file content part carrying the file_id inside the message content array — the server inlines the bytes for you:

{ "type": "file", "file": { "file_id": "<the uploaded id>" } }

Notes#

• Max 32 MB per file, 256 MB storage per account; files expire after 30 days.
• Supported types: images (png, jpeg, webp, gif), audio (mp3, wav, flac, m4a, ogg, aac), PDF, and plain text.
• The model must support the file's modality — vision for images, audio input for audio, file/PDF input for documents.
• List, retrieve, and delete are also available — see the Files guide for the full surface.

Also see#

• Files guide — endpoints, limits, and reference semantics
• Files reference