https://api.planasonix.comAuth:
Authorization: Bearer plus your API key or JWT.
CRUD and lifecycle
GET /api/pipelines
List pipelines.
Restrict to a project.
Restrict to a folder.
Match on pipeline name.
Filter by lifecycle status (
draft, active, archived, and so on).POST /api/pipelines
Create a pipeline with an initial graph.
Pipeline name.
Owning project.
Folder within the project.
Node definitions (
id, type, config, positions, and so on).Edge list (
source, target, optional port keys).GET /api/pipelines/{id}
Fetch the full graph and configuration.
Pipeline ID.
PUT /api/pipelines/{id}
Replace or update the pipeline graph (nodes and edges).
Pipeline ID.
Full node list when replacing the graph.
Full edge list when replacing the graph.
DELETE /api/pipelines/{id}
Soft-delete the pipeline (moves to trash).
Pipeline ID.
Runs and execution
POST /api/pipelines/{id}/run
Start a new run (full graph or parameterized subset, depending on body).
Pipeline ID.
Runtime variable overrides.
Execution environment (warehouse size, queue, and so on).
GET /api/pipelines/{id}/runs
Paginated run history for this pipeline.
Pipeline ID.
Page size.
Pagination cursor from
meta.GET /api/pipelines/{id}/execution-status
Current state of an in-flight or last completed execution.
Pipeline ID.
GET /api/pipelines/{id}/execution-plan
Logical execution plan (order, splits, pushes) for the current graph.
Pipeline ID.
GET /api/pipelines/{id}/lineage
Dataset-level lineage graph for the pipeline.
Pipeline ID.
GET /api/pipelines/{id}/column-lineage
Column-level lineage derived from the graph.
Pipeline ID.
Focus on outputs of a specific node.
GET /api/pipelines/{id}/query-plan
Engine query plan for SQL-heavy nodes (when supported by the backing system).
Pipeline ID.
Node to explain.
POST /api/pipelines/preview
Dry-run style preview without persisting outputs (limits and sandbox rules apply).
Graph fragment or full graph to preview.
Edges for the preview graph.
Optional connection IDs for preview-only execution.
POST /api/pipelines/optimize
Return suggestions to improve cost, parallelism, or pushdown.
Existing pipeline to analyze.
Inline graph when not referencing a saved pipeline.
Inline edges when not referencing a saved pipeline.
Metadata operations
POST /api/pipelines/{id}/clone
Duplicate the pipeline (optionally to another folder or project via body fields).
Source pipeline ID.
Name for the clone.
Target project.
Target folder.
PATCH /api/pipelines/{id}/rename
Rename only.
Pipeline ID.
New name.
PATCH /api/pipelines/{id}/move
Change folder (and optionally project if permitted).
Pipeline ID.
Destination folder ID.
Destination project when cross-project moves are allowed.
PATCH /api/pipelines/{id}/status
Update lifecycle status.
Pipeline ID.
Target status value.
Trash
GET /api/pipelines/deleted
List soft-deleted pipelines.
Filter by project.
POST /api/pipelines/{id}/restore
Restore from trash.
Pipeline ID.
DELETE /api/pipelines/{id}/permanent
Permanently delete a pipeline already in trash.
Pipeline ID.
Node preview and cache
POST /api/pipelines/{id}/nodes/{nodeId}/preview
Sample output for a single node using the saved graph context.
Pipeline ID.
Node ID within the graph.
Max sample rows.
POST /api/pipelines/{id}/nodes/{nodeId}/cache
Warm or invalidate cached intermediate results for a node (behavior is connector-dependent).
Pipeline ID.
Node ID.
For example
warm or invalidate.Related
Runs API
Poll and inspect individual runs.
Canvas
How graphs map to the visual editor.