ELT APIs
elt is Skippr Cloud’s managed ingest surface: a deployment and wrap of skipprd. You define pipelines and start runs through Cloud APIs; the platform runs skipprd for you (you do not install the binary for the default path).
Status: Preview — pipeline and run registry APIs are live in tables (CreatePipeline, StartRun, DescribeRun, GetPipeline, ListPipelines, UpdatePipeline, DeletePipeline, ListRuns, StopRun). Managed skipprd execution on compute (real sync/lake writes) is coming soon. For the self-hosted Skippr runner (CLI on your machines), see the ELT docs home.
Concepts
| Term | Meaning |
|---|---|
| Pipeline | Named source → sink definition in Cloud |
| Run | One execution with a run_id |
| Managed skipprd | Platform-run skipprd (Cloud default path) |
| Runner | Optional self-hosted skippr CLI — separate from managed Cloud elt |
Access (Cloud APIs)
| Hostname | elt.eu-central-1.cloud.skippr.io |
| Protocol | Cloud JSON (X-Amz-Target: CloudElt.*) |
| Auth | SigV4 (elt) / Cloud JWT via gateway |
| Region | eu-central-1 |
Operations
| Operation | Notes |
|---|---|
CreatePipeline | Register name, source, sink |
GetPipeline | Read pipeline metadata |
ListPipelines | Paginated tenant pipeline list |
UpdatePipeline | Replace source / sink |
DeletePipeline | Remove pipeline metadata |
StartRun | Returns run_id (Preview: registry status only) |
DescribeRun | Read run status |
ListRuns | Paginated runs; optional pipeline_name filter |
StopRun | Preview: marks PENDING/RUNNING runs FAILED |
| Pipeline schedules | Coming soon |
Self-hosted runner (optional)
Install and evaluate pipelines yourself (Snowflake, PostgreSQL, BigQuery, …):
- ELT home — overview and install
- Install
- How it works
- Source connectors
- Destination connectors
- CDC
That path is not how managed Cloud elt executes pipelines.