iCal Feeds

Every calendar has a public iCal feed URL. This endpoint serves RFC 5545 iCalendar data without API key authentication — the URL token is the access control.

Get an iCal feed

GET /ical/:ical_token.ics

Note

This endpoint is not under /v1/ and does not require an Authorization header. The random token in the URL is the sole access control.

Example

curl https://api.chronary.ai/ical/abc123def456.ics

Response 200 OK

Content-Type: text/calendar; charset=utf-8
ETag: "a1b2c3d4"
Cache-Control: public, max-age=300

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Chronary//API//EN
BEGIN:VEVENT
DTSTART:20260407T140000Z
DTEND:20260407T143000Z
SUMMARY:Strategy sync with Acme Corp
...
END:VEVENT
END:VCALENDAR

Conditional requests

The feed supports ETags. Send If-None-Match to avoid re-downloading unchanged data:

curl https://api.chronary.ai/ical/abc123def456.ics \
  -H "If-None-Match: \"a1b2c3d4\""

Returns 304 Not Modified if the feed hasn’t changed.

Caching

• Edge cache TTL: 5 minutes
• ETag support for conditional requests
• Rate limited by IP address

Errors

Status	Cause
404	Invalid or expired token
429	IP rate limit exceeded

Getting the feed URL

The ical_url is returned when you create or retrieve a calendar:

curl https://api.chronary.ai/v1/calendars/cal_x1y2z3 \
  -H "Authorization: Bearer chr_sk_test_your_key_here"

The response includes:

{
  "ical_url": "https://api.chronary.ai/ical/abc123def456.ics"
}

See the iCal Feeds guide for instructions on subscribing from Google Calendar, Apple Calendar, and Outlook.