---
title: "Start a new pipeline run for a saved and activated pipeline design"
method: POST
path: "/apps/{appId}/runs"
tags: ["Pipelines"]
---

# Start a new pipeline run for a saved and activated pipeline design

`POST /apps/{appId}/runs`

## Request

- Base URL: `https://pipeline-portal.home.mendix.com/api/v1`
- URL: `https://pipeline-portal.home.mendix.com/api/v1/apps/{appId}/runs`
- Auth: API key in header `Authorization`

Schedules a job on the server to start a new pipeline run. The job will be handled asynchronously; the operation returns a pipelineID that can be used to monitor the status of the process. Every request must be authenticated by a personal access token containing the scope `mx:pipelines:write`.

## Request body

- object
  - `pipelineId` string, uuid, required: UUID of the pipeline.

## Response `201`

Pipeline run is created. The Content-Location header can be used for the follow-up request to retrieve the run's status.

- Run: Details about the run.
  - `id` string, uuid, required: The unique run ID in UUID format.
  - `pipelineId` string, uuid, required: The unique pipeline ID in UUID format.
  - `pipelineName` string, required
  - `triggeredBy` User, required: The email of the user who triggered the pipeline run.
    - `email` string, email

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Access Denied
- `404`: Not Found

---

[API](https://skmtc.dev/mendix/apis/mendix-pipelines-api.md) - [All operations](https://skmtc.dev/mendix/apis/mendix-pipelines-api/llms.txt) - [OpenAPI document](https://skmtc.dev/mendix/apis/mendix-pipelines-api/revisions/54d51b38e0e3?raw)