Algolia Python API Docs | dltHub
Build a Algolia-to-database pipeline in Python using dlt with automatic cursor support.
Last updated:
Algolia is a search-as-a-service platform providing various APIs to index, search, and manage data. The REST API base URL is https://{APPLICATION_ID}.algolia.net and all requests require x-algolia-application-id and x-algolia-api-key headers.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Algolia data in under 10 minutes.
What data can I load from Algolia?
Here are some of the endpoints you can load from Algolia:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| search | /1/indexes/{indexName}/query | POST | hits | Searches an index using query string. |
| search_multiple | /1/indexes/*/queries | POST | results | Searches across multiple indices. |
| browse | /1/indexes/{indexName}/browse | POST | hits | Retrieves all records in an index. |
| get_objects | /1/indexes/*/objects | POST | results | Retrieves specific objects by ID. |
| get_object | /1/indexes/{indexName}/{objectID} | GET | Retrieves a single object by ID. |
How do I authenticate with the Algolia API?
Algolia uses header-based authentication, requiring both 'x-algolia-application-id' and 'x-algolia-api-key' headers in every request.
1. Get your credentials
To obtain your API credentials, log in to your Algolia dashboard. Navigate to the API Keys section (found in the settings menu). There, you will find your Application ID and existing API keys, such as the Admin API key, which has full administrative access, and Search-only keys. You can view, edit, or create new API keys with specific permissions (Access Control Lists) based on your integration requirements.
2. Add them to .dlt/secrets.toml
[sources.algolia_source] algolia_application_id = "your_application_id_here" algolia_api_key = "your_admin_or_search_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Algolia API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python algolia_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline algolia_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset algolia_data The duckdb destination used duckdb:/algolia.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /indexes/{indexName}/query and /indexes/{indexName}/browse from the Algolia API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def algolia_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{APPLICATION_ID}.algolia.net", "auth": {"type": "api_key", "api_key": api_key, "name": "x-algolia-api-key", "location": "header"}, }, "resources": [ {"name": "search", "endpoint": {"path": "1/indexes/{indexName}/query", "data_selector": "hits"}}, {"name": "browse", "endpoint": {"path": "1/indexes/{indexName}/browse", "data_selector": "hits"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="algolia_pipeline", destination="duckdb", dataset_name="algolia_data", ) load_info = pipeline.run(algolia_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("algolia_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM algolia_data.search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("algolia_pipeline").dataset() data.search.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Algolia data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Algolia?
Request dlt skills, commands, AGENT.md files, and AI-native context.