FruxonDocs
IntegrationsAssets

Lists supported content types for file upload ingestion.

Returns the MIME types and file extensions that `POST /assets:file` will accept. Use this to validate uploads client-side before submitting the multipart request. The list reflects parser availability in the RAG service and is identical for all tenants.

GET
/v1/tenants/{tenant}/assets:supportedTypes

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

tenant*string

The tenant identifier

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/assets:supportedTypes"
[
  {
    "extension": "string",
    "contentType": "string"
  }
]
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Lists available asset source types with their required and optional properties.

Returns the descriptors that drive asset creation: each entry lists the source type key (for example `google_drive`, `url`, `file`), its required and optional config parameters, and whether it supports OAuth. Use this to build the asset-creation form and to validate the `config` payload sent to `POST /assets`. Source types that report OAuth support must be authorized via `POST /assets:authorize` before creation.

Gets token and chunk usage statistics for an asset.

Returns aggregate counts across the asset's current index: indexed documents, chunks, and embedded tokens. Useful for billing dashboards and for sizing decisions before changing the token budget via `PATCH /assets/{asset}`. Reflects the current state of the index, not lifetime totals — deleted documents are excluded. For per-operation cost detail use `GET /assets/{asset}/operations`.