Search & Indexing

Updated

This family-level guide helps you find the main runtime endpoints used for search, suggestions, and indexing in Site Search apps. Use the linked endpoint articles for request parameters, examples, status codes, and response details.

Endpoint Family

Common endpoint suffixes in this family:

  • Search: /emselect
  • Suggest: /emsuggest
  • Update: /update

Note: Base URL patterns can vary by app and account configuration. The endpoint suffixes above are the documented contract.

Find these endpoint values in Site Search > App Settings > All APIs > Search & Indexing.

Search and Indexing endpoint family panel in Site Search app settings.

How To Use This Page

Use this page to identify which runtime endpoint family you need:

This overview intentionally avoids repeating endpoint-specific request tables and response contracts that are already maintained in dedicated articles.

Authentication

Authentication depends on the endpoint you call:

  • Search and suggest requests use read-capable credentials.
  • Update and ingest requests use write-capable credentials.

For exact auth formats, use the linked endpoint articles because Search, Auto-Suggest, and ingestion workflows do not all use the same credential pattern. For shared auth concepts, see Authentication and Authorization.

Shared Status and Limit Guidance

This endpoint family relies on the same platform-wide operational guidance used throughout the API docs:

  • 401 for missing or invalid authentication in supported auth flows.
  • 413 for oversized payloads.
  • 414 for oversized URLs or request lines.
  • 429 for rate or plan limit conditions.
  • Possible 500 responses during service-side failures or overage-related scenarios.

Use endpoint-specific articles for exact trigger conditions and example payloads.

  • Search API: query parameters, pagination, spellcheck, geospatial options, and response structure for /emselect.
  • Auto-Suggest API: prefix-based suggestion behavior and response payloads for /emsuggest.
  • Ingest API: write operations and update payload expectations for /update.
  • Ingest API Best Practices: batching, commit strategy, and operational guidance for indexing workflows.
  • Service Limits: shared payload, URL, and request-rate limits across this endpoint family.

Role Of This Article

Keep this page as a short navigation and orientation article for the Search & Indexing family. Endpoint-level implementation detail belongs in the dedicated runtime API articles.

Shared API Foundations

Use these shared references for authentication, request and response structure, and pagination behavior used across Site Search APIs:

Articles in this section