Custom HTTP headers sent with each webhook request (e.g. auth tokens)
string?WebhookOutputFormat
Response format sent to the webhook: ‘string’ (default) or ‘json’
string?WebhookSigningSecret
Shared signing secret used to sign webhook deliveries. When set, each request includes an HMAC-SHA256 signature of the request body in the ‘LC-Signature’ header (value ‘sha256=’). Recompute the HMAC over the raw request body with this secret to verify the delivery is authentic.
string?WebhookUrl
URL to receive webhook POST notifications
classClassifyResult:
Result of classifying a document.
requiredDoubleConfidence
Confidence score between 0.0 and 1.0
maximum1
minimum0
requiredstringReasoning
Why the document matched (or didn’t match) the returned rule
requiredstring?Type
Matched rule type, or null if no rule matched
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/for-agents/mcp/
- Other LlamaIndex tooling for agents — the LlamaParse Platform MCP server, agent skills and plugins, and the n8n node — is mapped at https://developers.llamaindex.ai/for-agents/