Update Records
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
each: the id field plus the fields to set (keyword, enum, identifier, number, date, geo, bool, and the acl / deny fields). null clears a field
Response
The region where this update applies, within about a second (GET …/updates shows when).
True when builds are published to every region: the next build started after this update carries it everywhere (one accepted while a build runs waits for the build after).
what still reflects the data before this update until the next build: typeahead, spelling and search_evidence (the no-typed-word answer) keep a deleted record’s words and do not learn a changed value’s words; hit_display: values shown on hits from the record’s mapped roles (rating, price, title…). Filters, sort, facets, hit.fields and GET change at once