A dedicated non-retaining workspace reviews TXT, CSV, or DOCX immediately and does not keep the customer content for search or workflows.
Non-retaining path
Use this only in a dedicated non-retaining workspace. It is not the stored quickstart with retention turned off. Uploaded stored collections, Catalog search, Smart Bite indexes, and workflows are not available on this path.
What it accepts
| Item | Limit |
|---|---|
| Formats | txt, csv, docx only. PDF, images, and spreadsheets are rejected |
| File size | 1,000,000 bytes |
| Schema | 1 to 32 fields. Each field has key, type (string, number, or boolean), and required. Optional description up to 1,000 characters |
| Instructions | Optional, up to 8,000 characters |
| Output | Up to 32,000 bytes |
| Deadline | 20 seconds |
DOCX must be a real Office Open XML document. Macro and active-content parts are rejected. CSV is checked as text. Nothing from this request is written into a collection.
In the product
- Select the non-retaining workspace. The settings badge says it is non-retaining.
- Provide a TXT, CSV, or DOCX file and a schema with the field types above.
- Review the result immediately. The review window is 900 seconds.
- Export JSON locally if you want a copy. The product does not keep the file, the answer, or a searchable index.
If capabilities are not ready, the extract call fails before it reads the file. A blocked processor is a failed run, not an empty success. Escalate with the error code (PROCESSOR_UNAVAILABLE or the reason code returned). Do not retry with a stored upload to “make the same request work.”
HTTP shape
POST /api/non-retaining/extract is a browser mutation. It requires the session cookie, a matching X-Bundata-Workspace header, and Content-Type: application/json. A non-browser bearer token is not this route’s client. GET /api/non-retaining/capabilities reports readiness for that same cookie session.
The JSON object has exactly format, bytesBase64, and schema, plus optional instructions. bytesBase64 is standard padded base64 of the file. The response is not stored. Do not log the file or the result in support tickets. Send the request id and error code only.
What you cannot do here
- Search the workspace or open a citation later. There is no stored source to open.
- Attach a workflow or a destination export.
- Use the fictional sample tour. That tour is the stored path.