Gets a single document by its ID.
Returns the document's metadata and current ingestion status, without its chunks. Use this when the listing-page payload is insufficient — for example to inspect the source URL or last-ingested timestamp of one document. To retrieve the document's indexed text fetch its chunks via `GET /assets/{asset}/documents/{document}/chunks`.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The asset ID.
uuidThe document ID.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/assets/497f6eca-6276-4993-bfeb-53cbbbba6f08/documents/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"id": "00000000-0000-0000-0000-000000000000",
"assetId": "00000000-0000-0000-0000-000000000000",
"fileName": "string",
"fileId": "string",
"contentType": "string",
"sourceUrl": "string",
"fileSize": 0,
"chunkCount": 0,
"status": "PENDING",
"errorMessage": "string",
"errorNextStep": "string",
"createdAt": 0,
"modifiedAt": 0,
"processedAt": 0,
"metadata": {}
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists all assets for the tenant, including token budget from the RAG service.
Returns the tenant's assets joined with RAG-side metadata (token budget, embedding model, usage) fetched in a single batch per page. Use this to render the assets index; for a single asset prefer the `GET /assets/{asset}` endpoint which avoids the batch join. Newly created assets appear immediately, but their ingestion may still be in progress — check `/operations` for status.
Gets a single ingestion operation by ID.
Returns the full state of one operation: progress counters, what went wrong if it failed and what to do about it, and computed embedding cost based on the asset's current pricing. This is the endpoint that clients should poll after `POST /assets`, `POST /assets:file`, or `POST /assets/{asset}:refresh` to detect completion. Polling cadence of a few seconds is appropriate; the underlying record is updated in place as workers make progress.