canonical: https://jentic.com/apis/polytomic.com/polytomic-api

# Polytomic API

Polytomic is a reverse ETL and data integration platform that moves data from warehouses and databases into business applications. The Polytomic API enables programmatic management of data sync configurations, connections to source and destination systems, and execution of bulk data operations. Data teams use it to automate customer data syncs to CRMs, push analytics results to marketing platforms, and keep operational systems updated with warehouse insights. The API manages connections to databases like Postgres and Snowflake, configures field mappings and transformation rules, and orchestrates sync execution with scheduling and error handling. It provides visibility into sync status, execution history, and data quality metrics. Polytomic enables reverse ETL workflows where analytics insights flow back into tools like Salesforce, HubSpot, and Intercom, activating data for operational use.

## For AI agents

Manage reverse ETL data syncs, connections, models, and bulk operations between warehouses and business applications.

## Scope

Provides reverse ETL from warehouses to business applications. Does not perform traditional ETL loading data into warehouses-use Fivetran or Airbyte. Does not provide data transformation-use dbt or warehouse SQL.

## Capabilities

- Create and manage connections to data warehouses and business application APIs
- Configure data models defining source queries and field mappings
- Set up sync jobs to continuously update destination systems from warehouse data
- Execute bulk sync operations for one-time data loads and backfills
- Monitor sync execution status and error logs for troubleshooting
- Query schema information from connected data sources
- Manage webhook configurations for sync event notifications

## Use cases

### CRM Enrichment from Data Warehouse Analytics

Revenue operations teams sync customer analytics from data warehouses to CRM systems, enriching lead and account records with usage metrics, product engagement scores, and predictive churn indicators. The API configures sync jobs that run hourly, querying warehouse views for customer aggregates and updating Salesforce fields. This enables sales teams to prioritize outreach based on product usage signals and marketing to segment audiences using behavioral data. Data teams use the API to version control sync configurations, deploy changes through CI/CD, and monitor data quality.

Example prompt: Create Polytomic connection to Snowflake data warehouse, configure model querying customer usage metrics, set up sync to Salesforce updating account records with engagement scores, schedule hourly execution, monitor sync status.

### Marketing Platform Audience Synchronization

Marketing teams activate warehouse segments in ad platforms and marketing automation tools for personalized campaigns. The API syncs audiences built from SQL queries (e.g., 'users who viewed pricing page but didn't convert') to Facebook Ads, Google Ads, and Braze. As warehouse data updates with new events, syncs propagate changes to keep marketing lists current. This eliminates manual CSV exports and ensures campaigns target the latest high-intent segments. Data teams configure syncs with field mappings for user identifiers, ensuring match rates remain high.

Example prompt: Configure Polytomic model with SQL query defining high-intent user segment, create sync to Facebook Ads custom audience, map user email field for matching, schedule sync to run daily after warehouse refresh, monitor sync success rate.

### Product Analytics Data Activation

Product teams push analytics insights to operational tools like Intercom, Zendesk, and customer success platforms so support and success teams act on user behavior. The API syncs user attributes (onboarding completion %, feature adoption score) and lifecycle stage from the warehouse to these tools. When a user qualifies as a power user, syncs update their Intercom profile triggering targeted in-app messages. This closes the loop between analytics and action, reducing time from insight to user impact.

Example prompt: Create Polytomic sync from warehouse user analytics table to Intercom user attributes, map feature adoption scores and lifecycle stage, configure real-time sync for high-value user updates, monitor sync errors and retry failures.

### Operational Database Backfills and Bulk Operations

Engineering teams use bulk sync operations to backfill operational databases with historical analytics, migrate data between systems, or seed production databases with warehouse transformations. The API's bulk sync endpoints enable one-time data loads controlled programmatically, useful during system migrations or data recovery scenarios. Unlike continuous syncs, bulk operations run once with retry logic for large datasets. Platform teams integrate bulk syncs into deployment pipelines, populating new microservice databases with customer context from the central warehouse.

Example prompt: Create Polytomic connection to destination database, configure bulk sync model with full historical query, execute bulk sync with monitoring, validate record counts match source query, handle errors and retry failed batches.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/connections` | List all configured connections |
| POST | `/connections` | Create a new connection to a data source or destination |
| GET | `/connections/{id}` | Get details for a specific connection |
| POST | `/bulk-syncs` | Create and execute a bulk sync operation |
| POST | `/bulk-syncs/{id}/start` | Start a bulk sync job |

## Key resources

- **Connections** — Manage data warehouse and application API connections.
- **Models** — Define source queries and field mappings for syncs.
- **Syncs** — Configure and execute continuous data synchronization jobs.
- **Bulk Syncs** — Run one-time data loads and backfill operations.
- **Schemas** — Query schema information from connected sources.

## Why Jentic

- **Setup:** Wiring Polytomic by hand means handling its bearer token auth and managing connection and sync configuration on every request yourself. Through Jentic you install once, import Polytomic from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Polytomic identifies connections and bulk syncs by id in the request path and body, so you limit the agent to the operations it needs, such as listing connections or starting a bulk sync. Operations you do not add, like creating new connections, are not available to it.
- **Credential handling:** Your Polytomic token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'sync customer data to Salesforce' or 'start a bulk sync', and Jentic returns the matching Polytomic operation with its input schema for connection and sync parameters so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Airbyte API** — An open-source data integration platform for syncing pipelines across sources and warehouses — an alternative to Polytomic.
- **Hevo Data** — A no-code ELT platform for automating data pipelines into your warehouse — an alternative to Polytomic.

## FAQ

### What authentication does the Polytomic API use?

The Polytomic API uses Bearer token authentication. You generate API tokens from your Polytomic organization settings and include them in the Authorization header for all requests.

### What is reverse ETL and how does Polytomic enable it?

Reverse ETL moves data from warehouses back into operational systems like CRMs and marketing tools, activating analytics insights for business use. Polytomic manages connections, field mappings, and sync orchestration so warehouse data continuously updates destination systems.

### Can I schedule automated syncs with the Polytomic API?

Yes, the API allows configuring sync schedules (hourly, daily, custom intervals) so data stays current without manual intervention. You can also trigger on-demand syncs via API for real-time use cases or testing.

### What data sources and destinations does Polytomic support?

Polytomic connects to major data warehouses (Snowflake, BigQuery, Redshift, Databricks) and business applications (Salesforce, HubSpot, Intercom, Google Ads, Facebook Ads). Check Polytomic's documentation for the full connector list.

### How do AI agents use the Polytomic API through Jentic?

Agents search Jentic for tasks like 'sync warehouse data to Salesforce' and receive Polytomic operation schemas. Jentic securely stores API tokens, handles authentication, and allows agents to configure connections, set up syncs, and monitor data operations with natural language instructions.

### Can I limit what my agent is allowed to do with the Polytomic API?

Yes. Because you run Jentic One yourself, you decide which Polytomic operations your agent can call, so you can allow it to list connections or start a bulk sync while withholding operations like creating new connections. Polytomic identifies connections and bulk syncs by id in the request path and body, and any operation you do not add is simply not available to the agent. Your Polytomic bearer token is stored by your own instance and injected at execution time, so the agent uses your access without ever seeing the credential.
