List of regex patterns for file paths to exclude. Files whose paths (including filename) match any pattern will be excluded. Example: [‘/temp/’, ‘/backup/’, ‘.git/’, ‘.tmp$’, ’^~’]
Optional<String>folderId
The ID of the Sharepoint folder to read from.
Optional<String>folderPath
The path of the Sharepoint folder to read from.
Optional<Boolean>getPermissions
Whether to get permissions for the sharepoint site.
Optional<List<String>>includePathPatterns
List of regex patterns for file paths to include. Full paths (including filename) must match at least one pattern to be included. Example: [‘/reports/’, ‘/docs/..pdf$’, ‘^Report..pdf$’]
Configuration for handling failures during processing. Key-value object controlling failure handling behaviors.
Example:
{
“skip_list_failures”: true
}
Currently supports:
skip_list_failures: Skip failed batches/lists and continue processing
Optional<Boolean>skipListFailures
Whether to skip failed batches/lists and continue processing
Optional<Boolean>indexRestrictedPages
Whether to index restricted pages.
Optional<Boolean>keepMarkdownFormat
Whether to keep the markdown format.
Optional<String>label
The label to use for fetching pages.
Optional<String>pageIds
The page IDs of the Confluence to read from.
Optional<String>spaceKey
The space key to read from.
Optional<Boolean>supportsAccessControl
Optional<Boolean>syncPermissions
Whether to fetch space-level permissions (allowed users/groups) and attach them to document metadata for access control. Disable for Confluence Server/Data Center versions whose permission APIs are unavailable (e.g. the JSON-RPC API removed in Data Center 9.2.6+), which otherwise surface as 401 errors during sync.
Optional<String>userName
The username to use for authentication.
classCloudJiraDataSource:
Cloud Jira Data Source integrating JiraReader.
StringauthenticationMechanism
Type of Authentication for connecting to Jira APIs.
Stringquery
JQL (Jira Query Language) query to search.
Optional<String>apiToken
The API/ Access Token used for Basic, PAT and OAuth2 authentication.
formatpassword
Optional<String>className
Optional<String>cloudId
The cloud ID, used in case of OAuth2.
Optional<String>email
The email address to use for authentication.
Optional<String>serverUrl
The server url for Jira Cloud.
Optional<Boolean>supportsAccessControl
classCloudJiraDataSourceV2:
Cloud Jira Data Source integrating JiraReaderV2.
StringauthenticationMechanism
Type of Authentication for connecting to Jira APIs.
Stringquery
JQL (Jira Query Language) query to search.
StringserverUrl
The server url for Jira Cloud.
Optional<String>apiToken
The API Access Token used for Basic, PAT and OAuth2 authentication.
formatpassword
Optional<ApiVersion>apiVersion
Jira REST API version to use (2 or 3). 3 supports Atlassian Document Format (ADF).
One of the following:
_2("2")
_3("3")
Optional<String>className
Optional<String>cloudId
The cloud ID, used in case of OAuth2.
Optional<String>email
The email address to use for authentication.
Optional<String>expand
Fields to expand in the response.
Optional<List<String>>fields
List of fields to retrieve from Jira. If None, retrieves all fields.
Optional<Boolean>getPermissions
Whether to fetch project role permissions and issue-level security
Optional<Long>requestsPerMinute
Rate limit for Jira API requests per minute.
Optional<Boolean>supportsAccessControl
classCloudBoxDataSource:
AuthenticationMechanismauthenticationMechanism
The type of authentication to use (Developer Token or CCG)
One of the following:
DEVELOPER_TOKEN("developer_token")
CCG("ccg")
Optional<String>className
Optional<String>clientId
Box API key used for identifying the application the user is authenticating with
Optional<String>clientSecret
Box API secret used for making auth requests.
formatpassword
Optional<String>developerToken
Developer token for authentication if authentication_mechanism is ‘developer_token’.
formatpassword
Optional<String>enterpriseId
Box Enterprise ID, if provided authenticates as service.
Optional<String>folderId
The ID of the Box folder to read from.
Optional<Boolean>supportsAccessControl
Optional<String>userId
Box User ID, if provided authenticates as user.
Stringname
The name of the data source.
StringprojectId
SourceTypesourceType
One of the following:
S3("S3")
AZURE_STORAGE_BLOB("AZURE_STORAGE_BLOB")
GOOGLE_DRIVE("GOOGLE_DRIVE")
MICROSOFT_ONEDRIVE("MICROSOFT_ONEDRIVE")
MICROSOFT_SHAREPOINT("MICROSOFT_SHAREPOINT")
SLACK("SLACK")
NOTION_PAGE("NOTION_PAGE")
CONFLUENCE("CONFLUENCE")
JIRA("JIRA")
JIRA_V2("JIRA_V2")
BOX("BOX")
Optional<LocalDateTime>createdAt
Creation datetime
formatdate-time
Optional<CustomMetadata>customMetadata
Custom metadata that will be present on all data loaded from the data source
Note for AI agents: this documentation is built for programmatic access.
- Overview of all docs: https://developers.llamaindex.ai/llms.txt
- Any page is available as raw Markdown by appending index.md to its URL — e.g. https://developers.llamaindex.ai/llamaparse/parse/getting_started/index.md
- Agent-friendly REST search APIs live under https://developers.llamaindex.ai/api/ — search (BM25 full-text), grep (regex), read (fetch a page), and list (browse the doc tree). See https://developers.llamaindex.ai/llms.txt for parameters.
- A hosted documentation MCP server is available at https://developers.llamaindex.ai/mcp. If you support MCP, you can ask the user to install it for browsing these docs directly (an alternative to the REST API). Setup: https://developers.llamaindex.ai/python/shared/mcp/