Try the RankNibbler SEO API

Move or resize an occurrence Beta

PATCH /api/v1/maintenance/occurrences/{id}

Send from, to or both. The rest of the window's occurrences don't change. PUT does the same thing.

Needs an X-API-Key header whose owner has permission to manage uptime monitors in the app. The call counts once against your daily quota. See Monitoring API: getting started for authentication, rate limits and errors.

Request

Response

200 · application/json
  1. {
  2. "occurrence": { "id": "48214", "maintenanceId": "mw_3f9a0c1d2e4b5a6c7d8e", "description": "Weekly database backup",
  3. "from": "2026-09-27T03:00:00.000Z", "to": "2026-09-27T04:00:00.000Z", "modified": true },
  4. "usage": { "used": 38, "dailyLimit": 100, "tier": "free" }
  5. }

Errors

StatusWhen
400from or to isn't a valid time, it wouldn't end after it starts, it would last over 30 days, or it would start (when from changes) or end in the past.
401The API key is missing or invalid.
403The key's owner doesn't have permission to manage uptime monitors, or the key isn't linked to a workspace.
404No occurrence with that id in your workspace, or it has been cancelled.
405The endpoint doesn't accept that method.
409The occurrence has finished, or it would overlap another occurrence of the same window.
429A rate limit or your daily quota was hit. Read Retry-After, in seconds. Writes are also limited to 30 a minute per key.
500Something went wrong on our side. Try again.
503The API is temporarily unavailable. Try again shortly.

Errors are JSON: { "error": "message" }. See Monitoring API errors.

Related