Archive stable site migration redirects

POST/v1/api/sites/{site_id}/migrations/projects/{migration_id}/archive-stable

Step 2 of 2. First call the preview, then send its confirmation_token here. Preview archive stable site migration redirects →

Archive the stable redirected URLs the preview showed; needs its token. Owner or admin.

Scope: sites:write
Token: OAuth access token only
Role: Owner or admin
MCP tool: archive_stable_migration_redirects · preview: MCP write tools are in preview; What scopes, tokens and roles mean →

Request

curl -X POST "https://api.crawle.io/v1/api/sites/11111111-1111-1111-1111-111111111111/migrations/projects/11111111-1111-1111-1111-111111111111/archive-stable" \
  -H "Authorization: Bearer $CRAWLE_ACCESS_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "X-Crawle-Confirmation: $CONFIRMATION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

const response = await fetch("https://api.crawle.io/v1/api/sites/11111111-1111-1111-1111-111111111111/migrations/projects/11111111-1111-1111-1111-111111111111/archive-stable", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CRAWLE_ACCESS_TOKEN}`,
    "Idempotency-Key": crypto.randomUUID(),
    "X-Crawle-Confirmation": confirmationToken, // from the preview response
    "Content-Type": "application/json",
  },
  body: JSON.stringify({}),
});
const data = await response.json();

import os
import uuid

import requests

response = requests.request(
    "POST",
    "https://api.crawle.io/v1/api/sites/11111111-1111-1111-1111-111111111111/migrations/projects/11111111-1111-1111-1111-111111111111/archive-stable",
    headers={
        "Authorization": f"Bearer {os.environ['CRAWLE_ACCESS_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
        "X-Crawle-Confirmation": confirmation_token,  # from the preview response
    },
    json={},
)
data = response.json()

$CRAWLE_ACCESS_TOKEN: is an OAuth access token from your integration's sign-in.
$CONFIRMATION_TOKEN: is the confirmation_token the preview step returned.
Idempotency-Key: is a new unique value for each new request.

Response 200JSON

{
  "applied": true,
  "archived_count": 1,
  "candidate_id": 1,
  "eligible_count": 1,
  "receipt_id": "example",
  "sample_urls": [
    "example"
  ],
  "skipped_existing_count": 1,
  "suppressed_count": 1,
  "website_id": 1
}

Example generated from the API contract.

Parameters

site_idpath · string (uuid)required
migration_idpath · string (uuid)required
X-Crawle-Confirmationheader · stringrequired: One-use confirmation_token returned by the matching preview route.1–256 characters
Idempotency-Keyheader · stringrequired: 1–180 characters

Request body

max_urlsinteger: 1–50000 · default 5000

Response 200

appliedbooleanrequired
archived_countintegerrequired
candidate_idintegerrequired
eligible_countintegerrequired
receipt_idstringrequired
sample_urlsarray of stringrequired
skipped_existing_countintegerrequired
suppressed_countintegerrequired
website_idintegerrequired

Errors

401
When
Missing, invalid, or expired token.
403
When
The token has none of the accepted scopes (sites:write).
403
When
Called with an API key. This endpoint needs an OAuth access token.
403
When
The person is not a workspace owner or admin.
422
When
The request did not match the schema. detail lists each problem.
429
When
Rate limited. Wait for Retry-After seconds.

Archive stable site migration redirects: errors
Status	When
401	Missing, invalid, or expired token.
403	The token has none of the accepted scopes (`sites:write`).
403	Called with an API key. This endpoint needs an OAuth access token.
403	The person is not a workspace owner or admin.
422	The request did not match the schema. `detail` lists each problem.
429	Rate limited. Wait for `Retry-After` seconds.

All errors and what to do →

Generated from the API contract at 7e7039b0b, synced October 30, 2026.