Overview
FileConfig API is an API for managing Fess file crawl configurations. You can configure crawl settings for local file systems, SMB/CIFS shared folders, FTP, and various object storage services.
Base URL
Note
All endpoints require administrator privileges and a valid access token. Refer to Admin API Overview for authentication details.
Endpoint List
| Method | Path | Description |
|---|---|---|
| GET | /settings | List file crawl configurations |
| GET | /setting/{id} | Get file crawl configuration |
| POST | /setting | Create file crawl configuration |
| PUT | /setting | Update file crawl configuration |
| DELETE | /setting/{id} | Delete file crawl configuration |
List File Crawl Configurations
Request
Note
The list endpoint is also accessible via PUT in addition to GET.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
page | Integer | No | Page number (1-based, default: 1) |
size | Integer | No | Number of items per page (default: 25, follows the paging.page.size setting) |
name | String | No | Filter by configuration name |
paths | String | No | Filter by crawl path |
description | String | No | Filter by description |
Response
total represents the total number of configurations matching the filter conditions.
Get File Crawl Configuration
Request
Response
Note
The response includes createdBy, createdTime, updatedBy, updatedTime, and versionNo, which are automatically populated by the server when a configuration is created or updated. versionNo is required when updating a configuration (see “Update File Crawl Configuration” below).
Create File Crawl Configuration
Request
Request Body
Field Description
| Field | Required | Description |
|---|---|---|
name | Yes | Configuration name (up to 200 characters) |
description | No | Configuration description (up to 1000 characters) |
paths | Yes | Crawl start paths (newline-separated for multiple paths). Specify using one of the following protocols: file:, smb:, smb1:, ftp:, storage:, s3:, or gcs: |
includedPaths | No | Regex pattern for paths to include in crawling |
excludedPaths | No | Regex pattern for paths to exclude from crawling |
includedDocPaths | No | Regex pattern for paths to include in indexing |
excludedDocPaths | No | Regex pattern for paths to exclude from indexing |
configParameter | No | Additional configuration parameters (key=value format, one entry per line) |
depth | No | Crawl depth (0 or greater) |
maxAccessCount | No | Maximum access count (0 or greater) |
numOfThread | Yes | Number of parallel threads (1 or greater) |
intervalTime | Yes | Access interval in milliseconds (0 or greater) |
boost | Yes | Search result boost value |
available | Yes | Enable/disable (string "true" / "false") |
sortOrder | Yes | Display order (0 or greater) |
permissions | No | Access permission roles (newline-separated for multiple values) |
virtualHosts | No | Virtual hosts (newline-separated for multiple values) |
Note
Audit fields such as createdBy, createdTime, updatedBy, and updatedTime are automatically set by the server and do not need to be included in the request body.
Response
Update File Crawl Configuration
Request
Request Body
When updating, id to identify the target configuration and versionNo are required in addition to the fields used at creation time. Specify the current value of versionNo as returned in the GET response.
Additional Fields for Update
| Field | Required | Description |
|---|---|---|
id | Yes | ID of the configuration to update (up to 1000 characters) |
versionNo | Yes | Current version number of the configuration to update. Use the versionNo value from the GET response. |
Response
Delete File Crawl Configuration
Request
Response
Path Formats
The following protocols can be used in paths (the supported protocols can be changed via the crawler.file.protocols setting).
| Protocol | Path Format |
|---|---|
| Local file | file:///path/to/directory |
| SMB/CIFS share | smb://server/share/path |
| SMB/CIFS share (SMB1) | smb1://server/share/path |
| FTP | ftp://server/path |
| S3-compatible object storage (MinIO, etc.) | storage://bucket/path |
| Amazon S3 | s3://bucket/path |
| Google Cloud Storage | gcs://bucket/path |
Note
Credentials (username and password) for SMB/CIFS or FTP access should not be embedded in the path. Configure them in the File Authentication settings instead. See File Authentication for details.
Usage Examples
Local File Crawl Configuration
Reference
Admin API Overview - Admin API Overview
WebConfig API - Web Crawl Configuration API
DataConfig API - Data Store Configuration API
File Crawling - File Crawl Configuration Guide
File Authentication - File Authentication Configuration Guide