Algolia
Algolia is a hosted search service. It powers the kind of search-as-you-type box that returns results on every keystroke, tolerates typos, and ranks the best matches first. In an app you build with Appsanic, you reach for Algolia when plain database queries feel slow or clumsy: searching a catalogue of products, a directory of people, a library of recipes, anything where users expect instant, forgiving results.
What you get by connecting it
Once Algolia is connected to the project, the agent can:
- Build an instant-search experience against your index, so results update live as the user types.
- Render typo-tolerant, ranked results without you touching any search library.
- Wire the search UI to the right index and surface the fields you care about.
Keeping the index populated and in sync is a separate server-side job. The agent can generate that job and setup instructions, but you deploy it and put a separate admin/indexing key directly in its secret manager. The connector neither accepts that key nor creates or syncs an index.
Connecting it
Algolia needs two values:
- An Application ID.
- A Search-only API key.
Find both in the Algolia dashboard under Settings then API Keys. Use a dedicated search-only key restricted to the intended indexes and limits. Everything reachable through a key embedded in the app must be safe for every user of that app to read. Leave the admin / indexing key server-side and never paste it into the connector or chat.
Open the project build, select Connectors, choose Algolia, and enter the Application ID and Search-only key. The connection applies only to that project and requires a paid plan. You can also open the same form from an in-chat connect card.
The Application ID and search-only key remain visible because they are intentionally publishable client configuration. Use Test now to verify the key is still read-only and accepted, or Disconnect to remove the project connection.
Keys and security
Algolia is a just-connect connector for existing, client-readable indexes. A search-only key cannot write, but it can expose every record it can query and consume quota. For private or per-user search, use a backend that issues short-lived secured Algolia keys with enforced filters, index restrictions, and rate limits instead of embedding the global connector key.
These two values are approved public connector metadata, so the browser connector UI and build prompt can receive them. The form rejects write-capable Algolia keys. Never put an admin/indexing key in this connector or in chat; keep it only in a deployed indexing backend's secret manager.
Useful links
- Algolia documentation: https://www.algolia.com/doc/
- Appsanic guide: In-App Search
Next
Read In-App Search for how search fits into the apps you build.