POST
/
pipelines
curl --location 'https://api.mixpeek.com/pipelines' \
--header 'Authorization: Bearer API_KEY' \
--header 'Content-Type: application/json' \
--data '{
    "connections": {
        "source": "source_conn_id",
        "destination": "destination_conn_id"
    },
    "transformation_code": "data.map(item => ({...item, newField: item.oldField * 10}))",
    "metadata": {
        "pipeline_name": "Data Enrichment",
        "description": "Enhances data by applying a transformation."
    }
}'
{
  "pipeline_id": "<string>",
  "enabled": true,
  "connections": {},
  "metadata": {}
}

Pipelines are the backbone of Mixpeek. It’s where you describe how you want the engine to process your objects as they pass through in real-time.

To build a pipeline, you’ll need to first have created a source and destination connection, then add their connection_id in the connections object.

Request

connections
object
required

Defines the source and destination connection identifiers for the data flow.

transformation_code
string
required

The code, provided as a string, which dictates how the data will be transformed during the pipeline process.

metadata
object

Optional metadata to provide context or additional information about the pipeline being created.

Response

pipeline_id
string
required

The unique identifier for the newly created pipeline. This ID can be used to reference the pipeline in future operations.

enabled
boolean

Indicates whether the pipeline is enabled upon creation. This can be set to true to start processing immediately.

connections
object
required

Echoes back the source and destination connection IDs provided in the request, confirming the data flow paths that have been set up.

metadata
object

Echoes back any metadata provided in the request, confirming the additional contextual information associated with the pipeline.