Skip to main content
Extraction endpoints return normalized document objects in outputs. Feed those documents to /v1/chunk, or use /v1/pipelines/ingest to run the full ingest workflow in one request.

Scrape URLs

POST /v1/ingest/url scrapes exact URLs or crawls a site.
Use POST /v1/ingest/url/stream for live crawl progress as server-sent events.

Parse Documents

POST /v1/ingest/docs parses server-accessible paths, folders, or file URLs.
POST /v1/ingest/docs/upload accepts multipart uploads from clients.
Upload multiple files by repeating files.
Multipart uploads are limited by server config. By default, /v1/ingest/docs/upload and /v1/pipelines/ingest/mixed accept up to 20 files and 50 MB per file. Set RAGRAILS_MAX_UPLOAD_FILES and RAGRAILS_MAX_UPLOAD_BYTES in the server environment to change those limits. Requests over either limit return HTTP 413.
Use /v1/pipelines/ingest/mixed when uploaded files must be indexed in the same pipeline request as server paths, folders, remote document URLs, websites, APIs, or Markdown.

Fetch APIs

POST /v1/ingest/api fetches one REST endpoint and converts the response into a document.
Batch API ingestion with apis is SDK-only for now. The REST schema currently requires url, so /v1/ingest/api examples use one endpoint per request.

Request Fields

Output Shape