# Cancel scheduled location archival

```http
POST https://api.synup.com/api/v4/locations/cancel_archive
```

Use this API to cancel the archival of locations that are scheduled for archival but have not yet been processed.

:::info[]

**Important Notes:**
- This endpoint can only cancel archival for locations that are in **ARCHIVE_SCHEDULED** status
- Once canceled, the location will return to **ACTIVE** status and can be updated as usual.
- Billing for the location will continue as per the standard cycle.

:::

Source: https://developer.synup.com/api/locations/cancel-scheduled-location-archival

## Header parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Content-Type` | string | required |  |

## Request body

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `input` | object | optional |  |
| `input.locationIds` | array of string | required | Array of location Node IDs to cancel archival for |

## Example request

```bash
curl -X POST 'https://api.synup.com/api/v4/locations/cancel_archive' \
  -H 'Authorization: API YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "input": {
    "locationIds": [
      "TG9jYXRpb246MTE4MzMzMA=="
    ]
  }
}'
```

## Responses

| Status | Description |
| --- | --- |
| `200` | Location archival cancellation successful |
| `400` | Bad request - invalid input |
| `401` | Unauthorized - invalid or missing API key |
| `403` | Forbidden - insufficient permissions |
| `404` | Location not found or not in ARCHIVE_SCHEDULED status |