Hevo Data

Name: Hevo Data API
Brand: Hevo Data
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsData Pipelinesbasic60 EndpointsREST

For Agents

Manage Hevo Data ELT pipelines — create sources and destinations, run pipelines on demand, pause objects, and trigger transformation models — using HTTP Basic auth with API key and secret.

Install Jentic One Beta

Connect the Hevo Data to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hevo Data, 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 Hevo Data API.

Create and configure pipelines that move data from source systems into a target warehouse without writing extraction code

Run a pipeline on demand with POST /api/public/v2.0/pipelines/{id}/run-now to backfill data outside the regular schedule

Pause, resume, or skip individual objects within a pipeline so a single broken table does not halt the whole flow

GET STARTED

Start building with Hevo Data API

Explore with Jentic

View OpenAPI Document

The Hevo Data API provides programmatic control over data pipelines, sources, destinations, models, and workflows on Hevo's no-code ELT platform. Across 60 endpoints, agents can list and create pipelines, run them on demand, pause and resume specific objects, manage transformation models, and trigger workflow executions. Authentication uses HTTP Basic with an API Key as username and API Secret as password, generated from Account > API Keys in the Hevo UI, and the API is region-scoped so callers must use the host that matches their account (us, us2, eu, in, asia, or au).

Use Cases

Patterns agents use Hevo Data API for, with concrete tasks.

★ Operational Pipeline Management

Use the Hevo API to monitor and recover pipelines without logging into the UI. Agents can poll GET /api/public/v2.0/pipelines for status, trigger POST /api/public/v2.0/pipelines/{id}/run-now after upstream issues, or pause specific objects with /pipelines/{id}/objects/{object_name}/pause when a schema change breaks a single table. This keeps the rest of the pipeline flowing while engineering investigates.

List pipelines with status=failed, then call POST /api/public/v2.0/pipelines/{id}/run-now on each to retry, capturing the new run id.

Programmatic Pipeline Provisioning

Provision new pipelines as part of a customer onboarding workflow. Create source and destination connections, attach them to a pipeline, set the schedule, and verify that the first sync completes — all from the API. Combined with infrastructure-as-code, this lets a data team add tenants without manual clicks in the Hevo console.

Create a pipeline named tenant-acme with source PostgreSQL and destination Snowflake, set schedule to every 60 minutes, then verify the first sync finishes.

Schema Evolution Handling

When a source schema changes, agents can detect the failing object via GET /api/public/v2.0/pipelines/{id}/objects/{object_name}/stats, pause the affected object with the pause endpoint, update the destination model, and resume — all without touching unrelated objects. This isolates blast radius and avoids manual escalation cycles.

Pause object orders in pipeline 1234 with POST /api/public/v2.0/pipelines/1234/objects/orders/pause, then resume it after the destination schema is updated.

AI Agent Data Operations

Through Jentic, an AI agent can answer 'why is the warehouse stale?' by calling Hevo's pipeline status endpoints and surfacing the failing object. Jentic holds the Basic auth credentials in the vault and exposes Hevo operations to the agent by intent, so the agent can chase down a stalled pipeline without seeing the API secret directly.

Search Jentic for 'list failed pipelines', execute the call against Hevo, then trigger run-now on the first result.

Key Endpoints

60 endpoints — the hevo data api provides programmatic control over data pipelines, sources, destinations, models, and workflows on hevo's no-code elt platform.

METHOD

PATH

DESCRIPTION

GET

/api/public/v2.0/pipelines

List all pipelines

POST

/api/public/v2.0/pipelines

Create a new pipeline

POST

/api/public/v2.0/pipelines/{id}/run-now

Trigger an immediate pipeline run

POST

/api/public/v2.0/pipelines/{id}/objects/{object_name}/pause

Pause a single object inside a pipeline

POST

/api/public/v2.0/pipelines/{id}/objects/{object_name}/resume

Resume a paused object

GET

/api/public/v2.0/pipelines/{id}/objects/{object_name}/stats

Get sync stats for a single object

PUT

/api/public/v2.0/pipelines/{id}/schedule

Update the pipeline schedule

GET

/api/public/v2.0/pipelines

List all pipelines

POST

/api/public/v2.0/pipelines

Create a new pipeline

POST

/api/public/v2.0/pipelines/{id}/run-now

Trigger an immediate pipeline run

POST

/api/public/v2.0/pipelines/{id}/objects/{object_name}/pause

Pause a single object inside a pipeline

POST

/api/public/v2.0/pipelines/{id}/objects/{object_name}/resume

Resume a paused object

Why Jentic?

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

Credential isolation

Hevo API Key and API Secret are stored encrypted in the Jentic vault. The runtime base64-encodes them into a Basic auth header at execution time so the agent never sees the raw secret.

Intent-based discovery

Agents search by intent (e.g., 'run a pipeline now' or 'pause a pipeline object') and Jentic returns the matching Hevo operation with its input schema, so the agent calls the right endpoint without scanning Hevo's docs.

Time to first call

Direct Hevo integration: 1-2 days for Basic auth handling, region routing, and pipeline status polling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Hevo Data API through Jentic.

What authentication does the Hevo Data API use?

Hevo uses HTTP Basic authentication: the API Key is the username and the API Secret is the password, both generated from Account > API Keys in the Hevo UI. Through Jentic, both values live in the encrypted vault and are concatenated and base64-encoded by the runtime, so the agent never sees the raw secret.

Can I trigger an immediate pipeline run with the Hevo Data API?

Yes. POST /api/public/v2.0/pipelines/{id}/run-now schedules an on-demand run for the specified pipeline. The response includes a run id you can correlate with subsequent GET /api/public/v2.0/pipelines/{id} polls to see when the run finishes and its status.

Which region should I call for the Hevo Data API?

Hevo is region-scoped — call the host that matches your account: https://us.hevodata.com, https://us2.hevodata.com, https://eu.hevodata.com, https://in.hevodata.com, https://asia.hevodata.com, or https://au.hevodata.com. Calling the wrong region returns 404 or auth errors even with valid credentials.

How do I pause a single failing table without stopping the whole pipeline through Jentic?

Search Jentic for 'pause a pipeline object', load the schema, and execute against POST /api/public/v2.0/pipelines/{id}/objects/{object_name}/pause. The other objects in the pipeline continue syncing; resume the paused object with the matching /resume endpoint once the schema is fixed.

What rate limits apply to the Hevo Data API?

Hevo does not publish a fixed rate-limit number in the spec, but heavy callers should batch list requests using the page and limit query parameters and back off on HTTP 429 responses. Most pipeline mutations also debounce — repeated run-now calls within a short window may be coalesced into a single run.

Hevo Data

Connect the Hevo Data to your agent

Capabilities

Start building with Hevo Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs