Skip to main content
Upload files that do not live on a website or in a repository, such as PDF manuals, Word documents or exported pages. Your own interface can read the ceilings before it sends anything, with Read the upload limits, so a file that is too large is refused by you rather than by a failed upload.

Supported files

The type is decided by the file extension. Legacy .doc files, spreadsheets and slide decks are not supported; export them to PDF or .docx first. Scanned PDFs without a text layer contain no extractable text.

Limits

  • Each file can be up to 1 MiB by default. Your MITHUNAI administrator sets this limit for the deployment and can raise it. The console does not show the figure, because it is deployment configuration; a file over the limit is refused with a message saying so.
  • Up to 1,000 files and 64 MiB per upload request.
  • If any file in a batch is unacceptable, the whole batch is refused and nothing is stored. Fix or remove that file and upload again.

Upload in the console

  1. Open Knowledge and select Connect a knowledge source.
  2. Choose File upload and select your file.
  3. Save. The file is stored and ingestion starts.

Upload with the API

Uploading is two steps: store the files, then register an upload source that refers to them.
1

Upload the files

The response lists the accepted files and includes a ready-made configuration object.
2

Register the source

Post the configuration from step 1 back unchanged:
3

Sync it

Sync the source to ingest the files, then follow the job as described in Ingestion.
In a script, pass the upload response’s configuration object straight into the source request rather than rebuilding it. Its files value is a newline-separated manifest that is easy to get wrong by hand.

Update an uploaded document

Upload the new version and create a new upload source for it, then delete the old source. Deleting a source removes its documents from retrieval immediately.
Last modified on September 27, 2026