Skip to main content
Use the Push to Algolia connector to transform your data and send it to Algolia using an API client.

Create a new Push to Algolia connector

  1. Go to the Algolia dashboard and select your Algolia .
  2. On the left sidebar, select Data sources.
  3. On the Connectors page, select Push to Algolia, then click Connect.
  4. Configure your transformation: create a new one or reuse an existing one.
  5. Configure your destination: create a new one or reuse an existing one.
  6. Create the task to generate a taskID.

Usage

Update your API client implementation to use either the WithTransformation helper methods of the Search API client or the pushTask method of the Ingestion API client.

Search API client WithTransformation helper methods

Set up transformation options

Before calling any WithTransformation method, set transformationOptions on the search client with your transformation region. Replace us with eu if your Algolia application uses the Europe analytics region. You can check your analytics region in the Infrastructure > Analytics section of the Algolia dashboard.
region is required. The client throws an error if you call a WithTransformation method without setting transformationOptions. transformationOptions creates a dedicated ingestion transporter that starts from the Ingestion API defaults (25-second timeouts, hosts derived from your region, and no compression) and only overrides the options you set. It doesn’t inherit the search client’s configuration. For more information, see Transformation options and the ingestion transporter. The WithTransformation helper methods are available for these Algolia API clients: C#, Dart, Go, Java, JavaScript, Kotlin, PHP, Python, Ruby, Scala, and Swift. If you target multiple destinations or run several Push connectors, use the pushTask method with a standalone Ingestion API client instead.
transformationOptions replaces the deprecated setTransformationRegion method (Java, C#, PHP), set_transformation_region method (Python), and transformation option (JavaScript). Those approaches forwarded the search client’s configuration to the ingestion transporter; transformationOptions uses the Ingestion API defaults instead. See your client’s upgrade guide to migrate.
To run the code examples on this page, install the latest API client.
These helper methods of the Search API replace the standard API clients methods (saveObjects, partialUpdateObjects, replaceAllObjects) but use the push method of the Ingestion API. They’re subject to the connector limits.
Use the helper methods if:
  • You already have an existing implementation using an API client.
  • You only have created one Push to Algolia connector for the you’re targeting.
The Collections feature creates its own (internal) Push connector. That means you can use the WithTransformation helper methods if you’re using collections and created an additional Push to Algolia connector.
  • Supported:
  • Not supported:
    • Multiple Push to Algolia connectors
If you have more than one Push to Algolia connector, use the pushTask method instead.

Save records with transformation

Replace saveObjects with saveObjectsWithTransformation.

Add or update attributes of multiple records with transformation

Replace partialUpdateObjects with partialUpdateObjectsWithTransformation.

Replace all records with transformation

Replace replaceAllObjects with replaceAllObjectsWithTransformation.

Ingestion API pushTask method

Use the pushTask method of the Ingestion API client if
  • You have multiple destinations linked to the index you’re targeting.
  • You have multiple Push to Algolia connectors, or a Push to Algolia connector and Collections.

Performance considerations

If you don’t need an Algolia-managed transformation, send records in batches using the regular API client methods to avoid processing overhead.

Supported indexing actions

The Push to Algolia connector supports all action types for batch indexing operations. For deleteObject, delete, and clear actions, it skips the transformation and uses traditional indexing instead.

Connector Debugger

To check and debug pushTask operations:
  • Check incoming events in the Connector Debugger on the Algolia dashboard. The eventID returned by a successful pushTask API call shows the status of the indexing operation.
  • To get real-time feedback, add the watch parameter to the pushTask API call. The response body reports errors and successes.

Limitations

This connector is subject to the following limitations:
Last modified on July 7, 2026