SDK API
Import Data Pipeline
Create a complete data pipeline from a JSON definition (API key auth)
POST
Single-shot pipeline creation. Accepts a declarative payload describing pipeline steps, schedule, and metadata — returns the created pipeline ID.
This endpoint uses API key authentication. Pass your key via
Authorization: Bearer trvh_sdk_... or x-api-key header.Request Body
Pipeline name displayed in the UI.
Optional description for the pipeline.
Pipeline category (e.g.,
"Real Estate", "E-Commerce").Tags for the pipeline (e.g.,
["adp", "mls", "automated"]).Where data comes FROM. This connection is inherited by all
source type steps.Where data goes TO. This connection is inherited by
load, stage, and reconcile steps.Ordered array of pipeline step definitions. Steps execute sequentially — each step depends on the previous one.
Optional schedule for automatic execution.
Step Type Configs
Source
Extract data from a database, API, file, or S3 bucket. InheritsconnectionId and connection config from the top-level source object. You typically don’t need a source step in the steps array — one is auto-generated from the top-level source definition. Only add explicit source steps when you need multiple sources (e.g., a second API call mid-pipeline for enrichment).
Override connection ID (for additional sources beyond the primary). If omitted, inherits from top-level
source.connectionId.Override API endpoint (for API sources).
Table name to extract from (for DB sources).
Transform
Field mapping and data transformation rules.Array of field mapping objects.
Array of transformation rules.
Validate
Data validation rules.Quality
Data quality checks.DB Lookup
Read from another database for reference/enrichment.Connection ID for lookup database.
Schema name.
Table to look up from.
Field from pipeline data to match on.
Field in lookup table to join on.
Comma-separated list of fields to pull from lookup table.
Stage
Write to a staging/temporary table for intermediate processing.Staging schema name.
Staging table/view name.
Load
Write to the final destination database (Postgres for v1). InheritsconnectionId, vendor, and schemaName from the top-level destination object.
Destination table name.
Override connection ID. If omitted, inherits from top-level
destination.connectionId.Override schema. If omitted, inherits from top-level
destination.schemaName.Reconcile
Post-load data reconciliation — compares source vs destination."default" uses the built-in ADP screen map. "custom" expects a mapping file at execution time.Compare source and destination row counts.
Check non-null completeness per field.
Run ADP screen-level validation.
Response
Whether the import succeeded.
The created pipeline document.