---
title: "Stop a flow"
method: POST
path: "/flows/{id}/stop"
tags: ["flows"]
---

# Stop a flow

`POST /flows/{id}/stop`

Stops the flow's integration process by publishing an appropriate event to the event bus. Requires the 'flows.control' permission.

## Path parameters

- `id` string, string, required

## Response `200`

Returns id and new status of the stopped flow

- object
  - `data` object
    - `id` string
    - `status` string
  - `meta` object

## Other responses

- `400` — Invalid ID format.
- `403` — User is not authorised to stop flows.
- `404` — No Flow with this id was found.
- `409` — Flow is currently not active. Only active flows can be stopped.

## Changes

- **2019-05-02** `eafe7d98cdb8` — 1 info
  - added the non-success response with the status `409`
- **2019-03-26** `a65fada07ca8` — 2 warning, 2 info
  - removed the optional property `header` from the response with the `200` status
  - removed the optional property `payload` from the response with the `200` status
  - added the optional property `data` to the response with the `200` status
  - added the optional property `meta` to the response with the `200` status

[Change history](https://skmtc.dev/openintegrationhub/apis/flow-repository/changes/flows/:id/stop/post.md)

---

[API](https://skmtc.dev/openintegrationhub/apis/flow-repository.md) · [All operations](https://skmtc.dev/openintegrationhub/apis/flow-repository/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/openintegrationhub/flow-repository/revisions/898fa794c6b8/schema)