Algolia Search API

Name: Search API
Brand: Search API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLEmbeddings SearchapiKey78 EndpointsREST

For Agents

Run search queries, index records, manage synonyms and rules, and administer keys and settings on Algolia indices.

Install Jentic One Beta

Connect the Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Search API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Search API.

Run single-index and multi-index search queries with facet filters via POST /1/indexes/{indexName}/query and /1/indexes/*/queries

Index, update, and delete records individually or in batches via /1/indexes/{indexName}/{objectID} and /1/indexes/{indexName}/batch

Search across facet values within a field for filter UIs via POST /1/indexes/{indexName}/facets/{facetName}/query

GET STARTED

Start building with Search API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for the Algolia Search API, keeping it validated and agent-ready. The Search API is Algolia's core surface - 78 endpoints covering query execution, indexing, synonyms, rules, dictionaries, API key management, clusters, vaults, and more. It serves single-index and multi-index queries, faceted filtering, browsing, batch object operations, and admin tasks like settings management and key rotation. The Search API is the foundation that the Recommend, Personalization, and Query Suggestions services build on.

Use Cases

Patterns agents use Search API for, with concrete tasks.

★ Storefront search with facets and filters

Run searches against a product index using POST /1/indexes/{indexName}/query, applying facet filters for category, brand, and price. Algolia returns ranked hits along with facet counts so the UI can render filter sidebars without a second request. The query response includes a queryID that should be passed to the Insights API on click and conversion events.

POST /1/indexes/products/query with query 'running shoes', facetFilters=[['brand:Nike','brand:Adidas']], hitsPerPage=24

Bulk catalog update via batch operations

Push a full daily catalog refresh by submitting batch operations to /1/indexes/{indexName}/batch. Each batch can include addObject, updateObject, partialUpdateObject, and deleteObject operations together, and the response returns a taskID you can poll until the operations are indexed. For multi-index updates use /1/indexes/*/batch.

POST /1/indexes/products/batch with 1000 addObject operations and poll the returned taskID via /1/indexes/products/task/{taskID}

Scoped API keys for frontend search

Generate a virtual API key scoped to a specific filter (for example, tenantID for multi-tenant SaaS) using POST /1/keys with restrictIndices and filters parameters. The resulting key can safely live in the browser because Algolia enforces the scope server-side, even if the key is intercepted.

POST /1/keys with acl=['search'], restrictIndices=['products'], and filters='tenantID:42' to generate a tenant-scoped key

Agent-driven catalog search and curation

An AI agent connecting through Jentic can search the catalog, propose synonyms or rules based on no-result queries, and apply changes - all without leaving the conversation. Jentic resolves intents like 'search Algolia products' or 'add an Algolia synonym' to the right endpoint and injects credentials from the vault.

Search Jentic for 'run an Algolia search query', load searchSingleIndex, and execute with the user's query and any facet filters extracted from the conversation

Key Endpoints

78 endpoints — jentic publishes the only available openapi specification for the algolia search api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/1/indexes/{indexName}/query

Run a search query on a single index

POST

/1/indexes/*/queries

Run multiple queries across indices

POST

/1/indexes/{indexName}/batch

Submit batch object operations

PUT

/1/indexes/{indexName}/{objectID}

Add or replace a record by objectID

POST

/1/indexes/{indexName}/browse

Browse the full index in pages

GET

/1/keys

List API keys

POST

/1/keys

Create a scoped API key

POST

/1/indexes/{indexName}/query

Run a search query on a single index

POST

/1/indexes/*/queries

Run multiple queries across indices

POST

/1/indexes/{indexName}/batch

Submit batch object operations

PUT

/1/indexes/{indexName}/{objectID}

Add or replace a record by objectID

POST

/1/indexes/{indexName}/browse

Browse the full index in pages

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

x-algolia-application-id and x-algolia-api-key are stored encrypted in the Jentic vault, with separate keys for search vs admin operations. Agents receive scoped tokens at request time and never see raw keys.

Intent-based discovery

Agents search Jentic by intent (e.g. 'run an Algolia search query', 'add a record', 'create a scoped API key') and Jentic returns the matching Search API operation with its input schema.

Time to first call

Direct integration: 2-3 days to wire query execution, batch indexing, key management, and retry logic. Through Jentic: under 1 hour - search, load schema, execute.

FAQs

Specific to using Search API through Jentic.

Why is there no official OpenAPI spec for the Algolia Search API?

Algolia ships SDKs but does not publish a standalone OpenAPI specification for the Search API. Jentic generates and maintains this spec so that AI agents and developers can call the Search API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Algolia Search API use?

Two API key headers: x-algolia-application-id and x-algolia-api-key. Different operations require different ACLs - 'search' for queries, 'addObject' for indexing, 'admin' for key management. Through Jentic, the appropriate key is fetched from the vault per operation.

Can I generate a public-facing key restricted to one tenant?

Yes. POST /1/keys with acl=['search'], restrictIndices, and filters such as 'tenantID:42'. Algolia enforces the filter server-side, so the resulting key is safe to embed in a browser even if it leaks.

What are the rate limits for the Algolia Search API?

Limits depend on your Algolia plan. Search queries scale per-cluster and indexing operations are queued. Watch for 429 responses with Retry-After headers and use /1/indexes/{indexName}/task/{taskID} polling rather than tight retry loops on indexing.

How do I run a search query through Jentic?

Search Jentic for 'run an Algolia search query', load searchSingleIndex, and execute with indexName, query, and any facet filters. Jentic injects the application ID and search key automatically.

Can I delete records by query?

Yes. POST /1/indexes/{indexName}/deleteByQuery with a filter expression and Algolia removes every matching record asynchronously. Poll the returned taskID to confirm deletion is fully indexed.

Algolia Search API

Connect the Search API to your agent

Capabilities

Start building with Search API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs