Ingestion and Documents API

Ingestion routes

• GET /v1/indexes/file-size-limit
• POST /v1/indexes/{index_id}/documents
• POST /v1/indexes/{index_id}/upload
• POST /v1/indexes/{index_id}/import/google-shopping
• POST /v1/indexes/{index_id}/ingest/cloud-complete
• POST /v1/indexes/{index_id}/ingest/start

Document routes

• GET /v1/indexes/{index_id}/documents
• GET /v1/indexes/{index_id}/documents/{doc_id}
• PATCH /v1/indexes/{index_id}/documents/{doc_id}
• DELETE /v1/indexes/{index_id}/documents/{doc_id}

Inline ingestion request

{
  "documents": [
    {
      "id": "sku_1001",
      "title": "PTFE Diaphragm Pump",
      "desc": "Chemical-resistant pump",
      "manufacturer": "LMI",
      "raw": {
        "category": "Pumps",
        "price": 499.99
      }
    }
  ]
}

Behavior notes

• write access is enforced for mutation routes
• ingestion waits for active jobs on the same index to finish before processing
• embeddings, suggestions, and optional graph enrichment are produced during ingestion
• account and index document limits can block writes with 409 responses

For the broader production picture around plan gating, upload ceilings, and operational constraints, see Service Limits.