---
title: "Start an ad-hoc full export of all active issues"
method: POST
path: "/cleanse-export/start"
tags: ["Cleanse Export"]
---

# Start an ad-hoc full export of all active issues

`POST /cleanse-export/start`

The export runs in a long-running background task with a distributed lock
to prevent concurrent exports. Progress can be tracked via the returned
export ID. Unlike the export phase of a cleanse analysis (which is
incremental), this always exports all active issues. It does NOT update
the incremental-export timestamp and does NOT send email notifications.

## Response `202`

Export started successfully

- StartExportResponse
  - `exportId` string, required — Unique identifier for the started export operation. Use this to poll progress.
  - `status` string, required — Initial status of the export (Pending).
  - `message` string, required
  - `startedAtUtc` string, date-time

## Other responses

- `409` — An export is already running

## Changes

- **2026-03-17** `2dc9a6322c1d` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/defra/apis/keeper-data-bridge-api/changes/cleanse-export/start/post.md)

---

[API](https://skmtc.dev/defra/apis/keeper-data-bridge-api.md) · [All operations](https://skmtc.dev/defra/apis/keeper-data-bridge-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/defra/keeper-data-bridge-api/revisions/0ab7d7a7a24f/schema)