Calendars
Resolve the registered public subscription URL
GET /calendars/{surface}
Request policy
- Operation
resolveCalendarSubscription- Access
- anonymous
- Automatic retries
- None
- Redirects
- Returned to the caller without following
- Request body limit
- No request body
- Pagination
- No collection iterator
Parameters
surface string required
Allowed: "activities" | "books" | "code" | "concerts" | "events" | "movies" | "music" | "photos" | "places" | "podcasts" | "reading" | "sports" | "tweets" | "videos" | "work" | "writing" | "feed"
Responses
302
Subscription URL; inspect with redirects disabled
Response headers
{
"Location": {
"schema": {
"type": "string",
"format": "uri"
}
}
}404
Unknown or unregistered calendar
text/plain
string
Examples
Examples use synthetic fixture values. Replace fixture identifiers with public IDs returned by the service. Request bodies and precise locations are transient; keep them out of logs.
curl
curl --fail-with-body --max-time 30 --max-filesize 16777216 --request GET 'https://irvinebroque.com/calendars/activities'TypeScript
import { PublicApi } from '@irvinebroque/public-api';
const api = new PublicApi();
const result = await api.calendars.resolve({
"surface": "activities"
});
console.log(result.status, result.headers.get('content-type')); // Keep transient capabilities in memory.CLI
irvinebroque calendars resolve --surface 'activities'The SDK preserves status, headers, and the server envelope. A 304 has no fresh body. Errors retain structured problem details; ordinary error messages omit response details. Responses are limited to 16 MiB and requests time out after 30 seconds by default.