Ingestion API

Name: Ingestion API API
Brand: Ingestion API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsData PipelinesapiKey61 EndpointsREST

For Agents

Create and run data connectors that ingest records from external sources into Algolia indices. Manage authentications, sources, destinations, tasks, and transformations programmatically.

Quickstart

Get started with Ingestion API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"ingest data into an Algolia index"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ingestion API API.

Create reusable authentication credentials and reference them across sources and destinations via /1/authentications

Schedule and trigger ingestion tasks that pipe records into Algolia indices via /2/tasks

Inspect run history and event-level diagnostics for any task via /1/runs and /1/events

GET STARTED

Start building with Ingestion API API

Explore with Jentic

View OpenAPI Document

Use for: I need to ingest a CSV file into an Algolia index, Set up a scheduled BigQuery to Algolia connector, List all ingestion tasks that failed in the last run, Retrieve the run logs for a specific ingestion task

Not supported: Does not handle search query execution, recommendations, or analytics events - use the Algolia Search, Recommend, and Insights APIs for those. Use this API for data ingestion connectors only.

Jentic publishes the only available OpenAPI document for Ingestion API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the Algolia Ingestion API, keeping it validated and agent-ready. The Ingestion API powers Algolia's no-code data connectors, letting you create sources, destinations, and tasks that pull data from external systems into Algolia indices on a schedule. It exposes 61 endpoints for managing authentications, sources, destinations, transformations, tasks, and run observability. Use it to wire up CSV, BigQuery, Shopify, or custom-Docker connectors and to monitor every ingestion run.

Use Cases

Patterns agents use Ingestion API API for, with concrete tasks.

★ Scheduled data warehouse to search index sync

Keep an Algolia index in sync with a BigQuery or Snowflake table by registering the warehouse as a source, defining a destination index, and creating a task that runs on a cron schedule. Transformations let you flatten nested rows and rename fields before they hit the index, and run logs surface any rows that failed validation.

Create a BigQuery source pointing at a products table, create a destination for an algolia index named 'products_prod', then create a daily task linking them and trigger an immediate run

E-commerce catalog ingestion from Shopify

Wire a Shopify storefront into Algolia in minutes by creating a Shopify source with the storefront's authentication, mapping it to a product destination index, and letting Algolia handle incremental pulls. The Ingestion API tracks each run and exposes per-record events so you can diagnose dropped or transformed rows.

Create a Shopify source with stored authentication ID 'shopify-prod-creds', link it to destination 'shopify-products' and run the resulting task

Custom HTTP source with JavaScript transformation

When the data lives behind a bespoke API, register a custom HTTP source, attach a JavaScript transformation that reshapes each record, and route the output to an Algolia index. The transformation runs server-side on Algolia, so agents do not need to maintain ETL infrastructure.

Create a transformation that lowercases the title field, attach it to a custom HTTP source, and validate the source before saving

Agent-driven ingestion automation

An AI agent operating through Jentic can search for ingestion intents, list current tasks, find failures by run status, and trigger reruns without leaving the conversation. Credentials are loaded from the Jentic vault so the agent never sees raw Algolia API keys.

Search Jentic for 'run an Algolia ingestion task', load the runSource operation schema, and execute it for sourceID 'src_abc123'

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/1/sources

Create an ingestion source

POST

/2/tasks

Create an ingestion task

POST

/1/sources/{sourceID}/run

Trigger an immediate run

POST

/1/push/{indexName}

Push records directly to an index

GET

/1/authentications

List stored authentications

POST

/1/transformations

Create a JavaScript transformation

POST

/1/sources

Create an ingestion source

POST

/2/tasks

Create an ingestion task

POST

/1/sources/{sourceID}/run

Trigger an immediate run

POST

/1/push/{indexName}

Push records directly to an index

GET

/1/authentications

List stored authentications

Why though Jentic?

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

Credential isolation

Algolia application IDs and API keys are stored encrypted in the Jentic vault. Agents request scoped tokens at execution time and never receive the raw x-algolia-api-key header value.

Intent-based discovery

Agents search Jentic by intent (e.g. 'ingest data into Algolia' or 'run an ingestion task') and Jentic returns the matching Ingestion API operations with their input schemas.

Time to first call

Direct integration: 1-2 days to wire up auth, source creation, task scheduling, and run monitoring. Through Jentic: under 30 minutes - search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Meilisearch API

Open-source search engine with self-hosted ingestion via direct document POSTs

Choose Meilisearch when self-hosting is required or when budget rules out Algolia's hosted ingestion plan.

Complementary

Algolia Search API

Query the indices that the Ingestion API populates

Use the Search API after Ingestion has loaded data to actually serve search queries.

Complementary

Algolia Monitoring API

Monitor cluster health while ingestion tasks are running

Use Monitoring to check infrastructure status if ingestion runs slow down or fail.

FAQs

Specific to using Ingestion API API through Jentic.

Why is there no official OpenAPI spec for the Ingestion API?

Algolia does not publish a standalone OpenAPI specification for the Ingestion API. Jentic generates and maintains this spec so that AI agents and developers can call the Ingestion 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 Ingestion API use?

Two API key headers: x-algolia-application-id and x-algolia-api-key. Through Jentic, both keys are stored in the Jentic vault and injected at execution time, so agent code never sees the raw key values.

Can I create a Shopify connector with the Ingestion API?

Yes. POST to /1/sources with type 'shopify' and a stored authentication ID, then link it to a destination via /2/tasks. The 61 endpoints cover the full source, destination, task, and run lifecycle.

What are the rate limits for the Algolia Ingestion API?

The spec does not declare numeric rate limits. Algolia enforces per-application throttling on ingestion runs and surfaces 429 responses with a Retry-After header when limits are hit. Plan for exponential backoff on task runs.

How do I trigger an ingestion task through Jentic?

Search Jentic with 'run an Algolia ingestion task', load the runSource operation, and execute it with the target sourceID. Jentic returns the run ID so the agent can poll /1/runs/{runID} for status.

Can I transform records before they reach the index?

Yes. Create a JavaScript transformation via POST /1/transformations and attach it to a source. Algolia runs the transformation server-side on each record, so no external ETL infrastructure is needed.