Public Calendar & Sharing
Public Link
Every calendar automatically receives a unique public link in the format:
https://www.kalender-tool.de/cal/{token}
This link can be accessed without login and shows the calendar in its configured default view. Visitors can switch between the views available for the owner's plan (Month, Week, Year β plus Day and List on Pro calendars).
Sharing Your Calendar
You can find your calendar's public link:
- In the Calendar Overview next to each calendar entry
- In the Calendar Detail View in the info area at the top
You can share the link in various ways:
- By email β Send the link directly to recipients
- On your website β Link the calendar on your webpage
- As a QR code β Create a QR code with the link for print materials
- Via social media β Share the link on social networks
iCal Feed
Every calendar offers an iCal feed at:
https://www.kalender-tool.de/cal/{token}/ical
Visitors can subscribe to this feed in their personal calendar (Google Calendar, Apple Calendar, Outlook). Changes are synchronized automatically.
Embedding via iframe
Kalender-Tool 2.0 offers two ways to embed a calendar on your own website. Ready-to-use <iframe> snippets are available directly in the calendar under the "Embed" tab.
Option 1: Full-page iframe (all plans)
Embeds the complete public calendar page β with header, view switcher, filter and navigation. Ideal for a dedicated calendar sub-page on your own website.
<iframe src="https://www.kalender-tool.de/cal/{token}"
width="100%" height="600" frameborder="0"></iframe>
- Available on Basic and Pro
- Automatically inherits your design settings (colors, font, logo)
- Views that your plan doesn't support are automatically hidden (see Calendar Views)
- Recommended height 600 px or more, width flexible
Option 2: Compact widget (Pro)
A slim widget (max. 400 px wide) that shows only the upcoming events in a reduced style β without navigation, without filters. Perfect for sidebars, landing pages, homepage blocks or info boxes.
<iframe src="https://www.kalender-tool.de/cal/{token}/widget"
width="400" height="500" frameborder="0"></iframe>
- Only available with a Pro subscription β without active Pro, the URL returns
403 Forbidden - Uses your primary and accent colors so the widget blends seamlessly into your site design
- Shows upcoming dates compactly stacked, optimized for narrow columns
- Recommended size: width 300β400 px, height 400β600 px
Tip: You can use both iframes on the same page β e.g. the compact widget as a sidebar teaser and link to the full calendar on a dedicated "Events" sub-page.
Comparison of Embed Variants
| Feature | Full-page iframe | Compact widget |
|---|---|---|
| Availability | All plans | Pro only |
| URL | /cal/{token} | /cal/{token}/widget |
| View switcher | Yes | No |
| Event filter | Yes | No |
| Navigation (prev/next month) | Yes | No |
| Best for | Dedicated calendar page | Sidebar, landing page, teaser |
| Recommended width | 600 px or more | 300β400 px |
JSON API (Pro)
A public, read-only JSON endpoint is available for developers, allowing you to query calendar data directly from your own application β for example your own website, a mobile app, a dashboard, or a smart-home display.
Endpoint
GET https://www.kalender-tool.de/api/calendar/{token}
Replace {token} with your calendar's public token β the same token used in the public link. You'll find it in the calendar overview and in the detail view next to the "Public Link" button.
URL Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
month | 1β12 | current month | Month for which events should be returned |
year | e.g. 2026 | current year | Year for which events should be returned |
The API always returns the events for the requested month. Recurring events are already expanded server-side into individual occurrences β the client doesn't need to understand RRULE logic.
Response Format
The API returns a JSON object with three blocks: calendar metadata, the requested period, and a flat list of all event occurrences in the month.
{
"calendar": {
"name": "Waste Collection 2026",
"description": "Collection dates for Sampletown",
"primary_color": "#4338CA",
"accent_color": "#E0E7FF",
"font_family": "Inter",
"layout": "month"
},
"month": 4,
"year": 2026,
"events": [
{
"id": 17,
"name": "Residual Waste",
"description": "Put out grey bin by 6:00am",
"date": "2026-04-06",
"icons": [
{ "id": 3, "name": "Residual", "file_path": "icons/system/rest.svg" }
]
},
{
"id": 17,
"name": "Residual Waste",
"description": "Put out grey bin by 6:00am",
"date": "2026-04-20",
"icons": [
{ "id": 3, "name": "Residual", "file_path": "icons/system/rest.svg" }
]
}
]
}
Field Reference
| Field | Content |
|---|---|
calendar.name | Calendar name |
calendar.description | Description (may be null) |
calendar.primary_color / accent_color | Hex colors to reuse in your own design |
calendar.font_family | Recommended font family |
calendar.layout | Owner-configured default view (month, week, day, list, year) |
month / year | Echo of the requested period |
events[].id | Internal event ID. Recurring events share the same id across entries. |
events[].date | Occurrence date as YYYY-MM-DD |
events[].icons | List of attached icons. file_path is relative to /storage/. |
Note: Multi-day events are returned as one entry per covered day. A 3-day event produces 3 entries with the same id and consecutive date values.
Status Codes
| Code | Meaning |
|---|---|
200 OK | Success β JSON object as described above |
404 Not Found | {"error": "Calendar not found"} β token doesn't exist |
403 Forbidden | {"error": "Subscription expired"} β owner's subscription is not active |
Example Calls
curl:
curl "https://www.kalender-tool.de/api/calendar/abc123-def456?month=4&year=2026"
JavaScript (fetch):
const token = 'abc123-def456';
const res = await fetch(`https://www.kalender-tool.de/api/calendar/${token}?month=4&year=2026`);
const data = await res.json();
data.events.forEach(e => console.log(e.date, e.name));
Typical Use Cases
- Your own website: Render your calendar on your municipal or club site β using your own design and framework.
- Mobile app: Show collection dates or events natively in your own app.
- Dashboards: Embed in office dashboards (e.g. Grafana, Home Assistant).
- Push notifications: A small worker calls the API daily and notifies users of upcoming events.
Rate limits & caching: Design your integration so that the API isn't polled multiple times per second. A 5β15 minute cache on your side is sufficient for most scenarios.
Plan availability: The JSON API is a Pro feature β if the calendar owner's subscription isn't active, the endpoint returns 403 Forbidden. For simple read-only access with minimal requirements, the public iCal feed is always available.
Control View via URL
| Parameter | Value | Result |
|---|---|---|
?view=month | month | Month view |
?view=week | week | Week view |
?view=day | day | Day view |
?view=list | list | List view |
?view=year | year | Year view |
Security
The public token is a UUID and practically impossible to guess. Only those who know the link can see the calendar. There is no public listing of all calendars.