GET only
Legacy routes are read-only projections. They do not create accounts, spaces, notes, bookings, or private data.
Compatibility surface
Small responses and a calendar for older clients.
Legacy exposes a narrow read-only bridge for systems that need predictable
HTTP text output instead of full JSON, ICS, or WebCal. It also serves one
fixed IE11/MSHTML calendar package at /calendar/.
New integrations should prefer OpenAPI or I/O.
Isolated transport
HTTP ends at the legacy boundary.
Modern Super-Calendar pages, APIs, accounts, and private data remain HTTPS-only. Plain HTTP is accepted only on the isolated legacy hostname for fixed public text routes and the local legacy calendar. Text routes request an allowlisted I/O projection from the main API over HTTPS; calendar files never proxy the modern app.
Legacy client
-> http://legacy.super-calendar.io/weather-summary
-> fixed allowlist, GET or HEAD, no credentials
-> https://super-calendar.io/api/weather/io/...
-> small public text response| Boundary | Policy |
|---|---|
| Main application | HTTPS only. |
| Legacy hostname | HTTP compatibility plus an HTTPS mirror. |
| Methods | GET and HEAD only. |
| Data | Public low-level text plus one fixed local calendar package. |
| Credentials | Never accepted or forwarded. |
| Routing | Fixed allowlist. No arbitrary URL or path forwarding. |
Scoped paths
Only documented allowlisted paths are served. Arbitrary proxying is not part of the contract.
Plain output
Text responses favor compact output. The calendar uses a local ES5-style runtime built for IE11/MSHTML.
Priority ladder
Pick the highest-level surface your client can use.
| Surface | Best for | Entry |
|---|---|---|
| OpenAPI | Modern API clients and generated SDKs. | /api/docs |
| I/O | Node, row, cell, CSV, TSV, NDJSON, and text projections. | /io/ |
| Legacy | Compatibility systems that need tiny text reads or the IE11 calendar. | /api/legacy |
| Agents | Machine-readable site and integration guidance. | /agents/ |
Examples
Current public compatibility routes.
GET http://legacy.super-calendar.io/health.txt
GET http://legacy.super-calendar.io/calendar/
GET http://legacy.super-calendar.io/weather-summary?charset=0
GET http://legacy.super-calendar.io/exchange-summary?charset=1
GET http://legacy.super-calendar.io/moon-summary?charset=2
GET http://legacy.super-calendar.io/seasons-summary
GET http://legacy.super-calendar.io/religion-summary
GET http://legacy.super-calendar.io/events-summary
GET http://legacy.super-calendar.io/custom-summary
GET http://legacy.super-calendar.io/holidays-summary
GET http://legacy.super-calendar.io/crypto-summary
GET http://legacy.super-calendar.io/earnings-summary
GET http://legacy.super-calendar.io/sports-summary
These routes are generated as thin mirrors of the public I/O catalog.
The canonical machine-readable contract is available at
/api/legacy.
Migration
Move to I/O when you can.
I/O gives the same low-level feel with stronger addressing, more formats, and direct resource manifests. Legacy exists for compatibility, not for new feature design.