GET /api/external/calendars/:id/ical
Re-fetch a saved calendar feed (Events tab / Refresh)

Request headers ↑

Only a registered user can perform this action
  Authentication - string - required
    Example of Authentication header : "Bearer TOKEN_FETCHED_FROM_SERVER_DURING_REGISTRATION"

Access ↑

A workspace calendar is reachable by any workspace user (incl. non-admins);
another user's personal calendar returns 404. last_synced_at is updated on
a successful NETWORK fetch only — a cache hit is not a sync, so it leaves
the timestamp alone rather than reporting a feed as fresher than it is.

Success response (200) ↑

Content-Type: text/calendar
Same raw-body proxy, caching and streaming behaviour as
POST /api/external/calendars/ical (the saved calendar's stored URL is
fetched); the two share one cache entry per feed URL. Nothing is parsed.

Error response body ↑

Same split as POST /api/external/calendars/ical: an upstream non-200 is
passed through, anything that never answered is a 422. A provider 404 still
carries the message below, so it cannot be confused with the 404 this
endpoint returns for a calendar the user may not access.
{
  "message": "The iCal URL you entered is not valid"
}

Error response body (403) — beta gate (GP-16587, temporary) ↑

While CALENDARS_BETA_ENABLED=true only users granted `calendars_enabled`
may call this endpoint; open to everyone once the variable is off.
{
  "message": "This feature is not available for your account yet.",
  "code": "feature_not_available"
}

Params

Param name Description
id
required

ID of a calendar accessible to the current user

Validations:

  • Must be a Integer
refresh
optional

Bypass the 15-minute cache and re-fetch from the provider (Refresh button)

Validations:

  • Must be one of: true, false, 1, 0, true, false.