DataImporter API

Name: DataImporter API API
Brand: DataImporter API
Availability: InStock

✓ Official Vendor SpecAnalyticsData Pipelinesbearer14 EndpointsREST

For Agents

Create data source connections, define field mappings, and trigger or cancel import jobs across the DataImporter pipeline platform.

Quickstart

Get started with DataImporter 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:
"trigger a data import job"

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

Capabilities

What an agent can do with DataImporter API API.

List, update, or delete configured connections to manage the pipeline inventory

Define field mappings between source columns and destination fields via POST /mappings

Trigger an import run with a specific connection and mapping via POST /imports

GET STARTED

Start building with DataImporter API API

Explore with Jentic

View OpenAPI Document

Use for: I need to start a CSV import into our destination system, List all configured DataImporter connections, Update a field mapping after the destination schema changed, Cancel an import job that's stuck

Not supported: Does not handle data scraping, BI dashboarding, or transformation logic beyond field mapping — use for source-to-destination import pipelines only.

DataImporter is a data import platform that connects external sources (CSV files, FTP feeds, SaaS APIs) to a destination system using configurable field mappings and import jobs. The REST API exposes three core resources — connections, mappings, and imports — letting integrators automate the lifecycle of a data pipeline: register a source, define how its fields map to the destination schema, then trigger and monitor import runs. Bearer token auth keeps the surface simple to integrate.

Use Cases

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

★ Automated Customer Data Onboarding

SaaS platforms onboarding new customers from legacy systems use DataImporter to programmatically register the customer's data source, attach a saved field mapping, and run an initial import — all without exposing the customer to the underlying ETL tooling. POST /connections registers the source, POST /mappings binds source columns to destination fields, and POST /imports kicks off the run. Engineering teams typically wire this into their onboarding flow in a couple of days.

Create a connection for an SFTP source, attach mapping ID 42, and trigger an import; poll GET /imports/{importId} until completion

Recurring Data Sync Orchestration

Data ops teams trigger nightly or hourly imports through the API rather than the platform UI, integrating DataImporter into their orchestration layer (Airflow, Prefect, Dagster). POST /imports starts the job, GET /imports/{importId} streams status, and POST /imports/{importId}/cancel aborts a run that exceeds a time budget. The pattern keeps DataImporter as the execution engine while orchestration logic lives in the team's existing scheduler.

Trigger a nightly import for connection ID 'salesforce-prod', wait for completion, and report row counts

Mapping Lifecycle Management

When a destination schema evolves, ops teams use the mapping endpoints to rotate field assignments without losing connection metadata. PUT /mappings/{mappingId} updates the field map, DELETE /mappings/{mappingId} removes a deprecated one, and GET /mappings lists everything currently in play. This avoids redoing connection configuration each time the target schema changes.

Update mapping 42 to add a new destination field 'lifecycle_stage' bound to source column 'stage', then re-run the linked import

AI Agent Pipeline Operations

Operations agents monitor import health by calling DataImporter through Jentic: searching for stuck imports, cancelling runaway jobs, or restarting failed runs with adjusted mappings. Jentic isolates the bearer token in its vault, so the agent only handles connection IDs and mapping IDs.

List imports from the last 24 hours, identify any in 'running' state for over 60 minutes, and cancel them via POST /imports/{importId}/cancel

Key Endpoints

14 endpoints — dataimporter is a data import platform that connects external sources (csv files, ftp feeds, saas apis) to a destination system using configurable field mappings and import jobs.

METHOD

PATH

DESCRIPTION

POST

/connections

GET

/connections

List configured connections

POST

/mappings

Create a source-to-destination field mapping

PUT

/mappings/{mappingId}

Update an existing mapping

POST

/imports

Trigger a new import job run

GET

/imports/{importId}

Get the status of an import job

POST

/imports/{importId}/cancel

Cancel a running import

POST

/connections

GET

/connections

List configured connections

POST

/mappings

Create a source-to-destination field mapping

PUT

/mappings/{mappingId}

Update an existing mapping

POST

/imports

Trigger a new import job run

Why though Jentic?

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

Credential isolation

DataImporter bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw bearer token never enters the agent's context or appears in tool-call traces.

Intent-based discovery

Agents search by intent (e.g. 'trigger a data import' or 'cancel an import job') and Jentic returns matching DataImporter operations with their input schemas, so the agent can call POST /imports or POST /imports/{importId}/cancel directly.

Time to first call

Direct DataImporter integration: 1-2 days for auth, polling logic, and mapping management. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Airtable API

Airtable is a common destination for DataImporter pipelines that need a structured, queryable target.

Use Airtable as the destination system and DataImporter to land raw data into it on a schedule.

Complementary

Supabase API

Supabase Postgres is another common destination for DataImporter feeds.

Use Supabase when the destination is a Postgres database your application reads from directly.

Alternative

Apify

Apify covers data collection from the web; DataImporter focuses on routing pre-existing data into destinations.

Choose Apify to scrape new data from the web; choose DataImporter when the source data already exists in CSV, SFTP, or another connected system.

FAQs

Specific to using DataImporter API API through Jentic.

What authentication does the DataImporter API use?

DataImporter uses HTTP bearer token authentication on every endpoint. Through Jentic, that bearer token is stored encrypted in the MAXsystem vault and injected at call time, so the agent only ever handles connection and import IDs.

Can I trigger an import job with the DataImporter API?

Yes. POST /imports starts a new import using a previously configured connection and mapping; the response returns an importId you can poll via GET /imports/{importId} or stop with POST /imports/{importId}/cancel.

What are the rate limits for the DataImporter API?

Rate limits are not declared in the OpenAPI spec; check the DataImporter dashboard or contact support for plan-specific concurrency and monthly run quotas before scheduling tight loops.

How do I create a new source connection through Jentic?

Search Jentic for 'create a data import connection', load the POST /connections operation, and execute it with your source configuration. Jentic injects the bearer token automatically and returns the new connectionId.

Can I cancel a stuck import job via the API?

Yes. POST /imports/{importId}/cancel stops an in-flight import and is the right call when an upstream source hangs or the run exceeds its time budget.

Does the DataImporter API expose mapping CRUD?

Yes. Full lifecycle is covered: GET /mappings lists configurations, POST /mappings creates one, PUT /mappings/{mappingId} updates, and DELETE /mappings/{mappingId} removes it. Mappings can be reused across multiple connections.