Import From Algolia
Copy an Algolia index into this index: send an export of it, or read access to it. Importing into an index that already has records deletes all of them and adds the Algolia records in their place. Read access answers 202 with an import job that builds the index when it ends. An export answers 200 with what was mapped; send build: true to start the build too. Importing into a new index takes a write key for every index. Algolia keys are never stored.
Authentication
A write key, issued by Captain. Server side only. Sent as Authorization: Bearer <key>.
Path parameters
Headers
Replays within 24 hours return the stored response (header Idempotent-Replayed: true). The same key on a different request answers 422. A concurrent duplicate answers 409. Failed requests do not keep the key.
Request
Response headers
the last update seq search had applied when this request started; the answer reflects at least that much (GET …/updates applied_seq). Not on 401 or 403, nor for an index this server does not have
the index’s incarnation, an opaque string: it changes only when the index is deleted and created again (whose seqs start again at 1), or restored from a backup (whose seqs continue from the backup’s). Sent with X-Captain-Applied-Seq
Response
An export: the records were added, with what was mapped. The build starts only with build: true (build_job).
flexible schema: one entry per (dotted) field
per section {mapped, approximated, not_mapped}, and records
what could not be read (for example no settings ACL)
true: an import sent with object_search true (settings and effective instead of schema)
true: a preview. Nothing was stored; records counts the records that would be added
with object_search: the settings the Algolia settings mapped to
object_search: the field table the next build uses