---
title: "Cancel Scheduled Quota Change"
description: "Cancels a quota reduction that was scheduled for the end of the current billing period, so the organization keeps its current plan. Answers cancelled:false — not 404 — when nothing is scheduled."
---

`DELETE /api/organizations/:organizationPublicId/pending-quota-change`

## Example (cURL)

```bash
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"
ORG_ID="<organization-public-id>"

curl -X DELETE "$BASE_URL/api/organizations/$ORG_ID/pending-quota-change" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Accept: application/json"
```

Notes:

- This endpoint takes no request body. It closes whichever quota reduction is currently scheduled for the organization; there is never more than one.
- A quota reduction does not take effect immediately. Under AGB § 10.5 it is scheduled for the end of the current billing period and is returned as `pendingQuotaChange` (see [Update Organization](/api/organization/update-organization) and [Get Organization Details](/api/organization/get-organization-details)). This endpoint is what calls it off before it fires.
- **This is the only way to keep the current plan.** Direction is classified against the organization's *current* — still higher — tier, so re-sending the current tier through `PATCH` counts as an unchanged request and leaves the scheduled reduction in place. Only a genuine price increase supersedes one, and that changes the plan rather than restoring it.
- Cancelling is free and always allowed until the change applies. Afterwards there is nothing left to cancel: the reduction is already the organization's plan, and going back up is an ordinary quota increase through [Update Organization](/api/organization/update-organization).
- Requires organization write access (organization admin or global admin) from an unrestricted session or token — the same authorization as [Update Organization](/api/organization/update-organization). A customer-scoped API token cannot call this endpoint, even with `admin`-level role, because cancelling changes what the organization pays from the next period onwards.

## Response

```json
{
  "cancelled": true
}
```

| Value | Meaning |
| --- | --- |
| `true` | A scheduled reduction was open and has been cancelled. The organization keeps its current plan. |
| `false` | Nothing was scheduled, so nothing changed. **This is a success, not an error** — the endpoint is deliberately idempotent so that a repeated call (a double-clicked button, a retried request) does not surface a failure. |

## Common errors

- `401 Unauthorized` (`data.code: unauthorized`) when you are not logged in
- `400 Invalid Organization identifier` when `:organizationPublicId` is neither a legacy integer id nor a valid UUID public identifier
- `403 Forbidden` (`data.code: forbidden`) when you do not have write access to the organization
- `403 Forbidden` (`data.code: customerScopedTokenForbidden`) when called with a customer-scoped API token; this is an organization-wide action and requires an organization-scoped token or a session
- `404 Organization not found` (no `data.code`) when `:organizationPublicId` does not resolve to an existing organization

Note that there is no "nothing to cancel" error — that case is `200` with `cancelled: false`.

See [Error Codes](/api/error-codes-and-known-pitfalls) for the full list.