Skip to content
Docs›Migration

Algolia Compatibility Guide

DocSlurp exposes an Algolia-style compatibility surface for queries, settings, synonyms, rules, analytics, and import flows so search migrations can happen incrementally instead of as a rewrite.

SDK
Client Shim
import { docslurpAlgoliaClient } from '@docslurp/compat-algolia'

const client = docslurpAlgoliaClient({
  apiUrl: process.env.PUBLIC_DOCSLURP_API_URL,
  clientKey: process.env.PUBLIC_DOCSLURP_CLIENT_KEY
})

const index  = client.initIndex(WORKSPACE_ID)
const result = await index.search({
  query:   'invoice',
  filters: 'tag:finance AND mime_type:application/pdf'
})
Supported endpoints: query, multipleQueries, settings, synonym batch sync, rule batch sync, analytics event intake, analytics summaries, and a generic importer for Algolia, Elastic, and legacy parser metadata exports.
CLI
Migration CLI
docslurp import-search-compat export.json \
  --workspace <workspace-id> \
  --source    algolia \
  --api-url   https://api.docslurp.example \
  --api-key   $DOCSLURP_API_KEY
Elastic exports map searchable fields and keyword facets into DocSlurp compatibility settings, while Algolia exports preserve settings, synonyms, rules, schema hints, and migration metadata for auditability.