Restore a deleted event

POSThttps://<your-url>/api/v2/events/{event}/actions/restore

MCP id events.actions.restore

Clears the soft-delete marker and returns the event in the detail view, putting it back on its owner's agenda.

Token scope: api:write:events
Without it: 403 insufficient-token-scope.
Permission: events::manage_self
Without it: 403 insufficient-permission.
Rate cost: 1 unit, write bucket. A write costs the same whatever view you ask for.
Also: Accepts Idempotency-Key. Accepts If-Match. Never cached: private, no-store. Unknown query parameters are refused, never ignored.

Both are checked, scope first. A token never does more than its user. How access is checked

Request

Example: Restore a deleted event

curl -X POST \
  'https://<your-url>/api/v2/events/1/actions/restore' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <key>' \
  -d '{}'

const response = await fetch('https://<your-url>/api/v2/events/1/actions/restore', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer <token>',
    'Accept': 'application/json',
    'Content-Type': 'application/json',
    'Idempotency-Key': '<key>',
  },
  body: JSON.stringify({}),
});

use Illuminate\Support\Facades\Http;

$response = Http::withToken('<token>')
    ->acceptJson()
    ->withHeader('Idempotency-Key', '<key>')
    ->post('https://<your-url>/api/v2/events/1/actions/restore', [
    ]);

import requests
response = requests.request(
    'POST',
    'https://<your-url>/api/v2/events/1/actions/restore',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json', 'Content-Type': 'application/json', 'Idempotency-Key': '<key>'},
    json={},
)

Response

The shape of the response, with sample values.

{
  "data": {
    "id": 1,
    "user_id": 1,
    "task_id": 1,
    "parent_event_id": 1,
    "occurrence_date": "2026-03-04",
    "start": "2026-03-04T09:15:00Z",
    "end": "2026-03-04T09:15:00Z",
    "title": "…",
    "description": "<p>…</p>",
    "is_all_day": false,
    "is_recurring": false,
    "recurrence_interval": 1
  },
  "meta": {
    "warnings": [
      {
        "…": "6 fields of warnings"
      }
    ]
  }
}

{
  "type": "https://developers.plnnrly.com/api/v2/problems/idempotency-key-in-flight",
  "title": "Idempotency key in flight",
  "status": 409,
  "detail": "The original request for this Idempotency-Key is still being processed. Retry shortly.",
  "instance": "/api/v2/worklogs",
  "request_id": "01K4B7Q9YV3PZ2N8T1E6M0XR4S"
}

{
  "type": "https://developers.plnnrly.com/api/v2/problems/precondition-failed",
  "title": "Precondition failed",
  "status": 412,
  "detail": "The record changed since the version named in If-Match. Re-read it and retry.",
  "instance": "/api/v2/work-items/812",
  "request_id": "01K4B7Q9YV3PZ2N8T1E6M0XR4S",
  "current_version": 12
}

11 more fields, listed under Response

Restoring somebody else's event additionally requires events::manage_for_others, on top of events::manage_self. Restoring an event that is not deleted succeeds and returns an already_in_target_state warning, so a retry is safe. On a recurring master this brings the whole series back. The restore reaches a deleted event without the trashed parameter and does not accept it.

Path parameters

eventintegerRequired

The Event's numeric id. Accepts a soft-deleted record.

Query parameters

Unknown parameters are refused with 400, naming the parameter.

viewstring

Which field set to render.

summarydetaildefault

Request headers

X-Request-Idstringpattern

A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.

If-Matchstring

The ETag a write is conditional on. A stale validator is 412 precondition-failed.

Idempotency-Keystring≤ 255

A caller-chosen key that makes this POST safe to retry. Replaying it returns the original response with Idempotency-Replayed: true.

Response 200

Returns a Event in the detail view.

Headers

ETag: A strong validator of exactly this representation.
Idempotency-Replayed: true when this response was replayed from a stored Idempotency-Key rather than produced by a new write.
RateLimit: The IETF httpapi-ratelimit-headers form of your remaining allowance on the tightest bucket this request touched.
RateLimit-Policy: The ceiling and window of that bucket, as <limit>;w=<seconds>.
X-Request-Id: The server-generated ULID correlating this response with our logs.

Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning

idinteger

Unique identifier.

user_idintegerServer-assigned

Whose agenda the event is on. Always the authenticated user at creation time; not writable.

task_idinteger or null

Kanban task this event is planned against, or null for a plain calendar block. Only an event with a task can have time logged on it.

parent_event_idinteger or nullServer-assigned

Master event, when this row is a separated occurrence of a recurring series. Set by the server; not writable.

occurrence_datedate (YYYY-MM-DD) or nullServer-assigned

The date of the series occurrence this row replaces. Set by the server; not writable.

starttimestamp (YYYY-MM-DDThh:mm:ssZ)

When the event starts. RFC 3339 UTC.

endtimestamp (YYYY-MM-DDThh:mm:ssZ)

When the event ends. RFC 3339 UTC.

titlestring≤ 255

Event title, as shown on the calendar tile.

descriptionhtml or nullDetail only

Free-text description, authored in the rich editor. HTML, sanitised on the way in and on the way out; @-mention spans are preserved, and changing them is what notifies the people mentioned.

is_all_dayboolean

Whether the event occupies whole days rather than a time range. An all-day event is measured against the owner's working week rather than against start and end.

is_recurringboolean

Whether this row is the master of a recurring series. When true, the recurrence fields describe how occurrences are generated.

recurrence_intervalinteger or null

How many frequency units pass between occurrences: 2 with a weekly frequency is every other week.

recurrence_frequencystring or null

The unit the series repeats in.

dayweekmonthyear

New values may be added.

recurrence_patternstring or null

How a monthly or yearly series positions its occurrence within the month. Ignored for a daily or weekly frequency.

day_of_monthweekday_occurrence

New values may be added.

recurrence_starttimestamp (YYYY-MM-DDThh:mm:ssZ) or null

First moment the series may generate an occurrence.

recurrence_endtimestamp (YYYY-MM-DDThh:mm:ssZ) or null

Last moment the series may generate an occurrence; null for an open-ended series.

selected_weekdaysarray of string or nullDetail only

Weekdays a recurring event falls on. Applies to a weekly frequency; ignored otherwise.

monday
tuesday
wednesday
thursday
friday
saturday
sunday

New values may be added.

recurrence_exceptionsarray of string or nullDetail only

Dates on which this recurrence does not occur. plnnrly adds one whenever a single occurrence is separated or deleted.

created_attimestamp (YYYY-MM-DDThh:mm:ssZ)

Creation timestamp.

updated_attimestamp (YYYY-MM-DDThh:mm:ssZ)

Last-write timestamp; use for incremental sync.

deleted_attimestamp (YYYY-MM-DDThh:mm:ssZ) or null

When the event was deleted, or null while it is live. Reach a deleted event with trashed=with and undo it with POST events/{event}/actions/restore.