SuggestAPI supports a staged index lifecycle through logical indexes and active physical index IDs.

Typical rollout pattern

  1. Create a logical index.
  2. Allocate a new physical index ID.
  3. Build or reindex content into the staged physical target.
  4. Validate schema, counts, and search results.
  5. Promote the staged physical index to live traffic.

Useful endpoints

  • POST /v1/indexes
  • POST /v1/indexes/{index_id}/allocate-physical-id
  • POST /v1/indexes/{index_id}/reindex
  • POST /v1/indexes/{index_id}/promote
  • GET /v1/indexes/{index_id}/stats
  • GET /v1/indexes/{index_id}/tasks

Why this matters

This pattern lets you:

  • rebuild large indexes without taking production search offline
  • validate new schema and ranking settings before cutover
  • separate indexing jobs from live traffic