---
title: "Archive a journey"
method: DELETE
path: "/projects/{projectId}/journeys/{journeyId}"
tags: ["Swarms"]
---

# Archive a journey

`DELETE /projects/{projectId}/journeys/{journeyId}`

ARCHIVES rather than deletes, and the response says so. Existing runs keep pointing at the definition they executed, so their history stays readable.

## Response `200`

The journey was archived.

- JourneyArchived — Journeys ARCHIVE rather than delete: existing runs keep pointing at the definition they executed.
  - `id` string, required
  - `projectId` string, required
  - `archived` true, required

## Other responses

- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/d3adfe49fbbf/schema)